<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/python, branch debian/squeeze-backports</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fsqueeze-backports</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fsqueeze-backports'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-05-24T01:32:02Z</updated>
<entry>
<title>python: Remove find_message_by_filename workaround</title>
<updated>2012-05-24T01:32:02Z</updated>
<author>
<name>Austin Clements</name>
<email>amdragon@MIT.EDU</email>
</author>
<published>2012-05-18T04:13:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=54508eb78d1c5c1c67c8b220cf2bd826af1203a9'/>
<id>urn:sha1:54508eb78d1c5c1c67c8b220cf2bd826af1203a9</id>
<content type='text'>
Now that notmuch_database_find_message_by_filename works on read-only
databases, remove the workaround that disabled it on read-write
databases.

This also adds a regression test for find_message_by_filename.
</content>
</entry>
<entry>
<title>python test "compare message ids"</title>
<updated>2012-01-08T12:46:50Z</updated>
<author>
<name>Patrick Totzke</name>
<email>patricktotzke@googlemail.com</email>
</author>
<published>2012-01-02T14:51:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ab69d6efa0e095e0bff24f77220797c58068cc08'/>
<id>urn:sha1:ab69d6efa0e095e0bff24f77220797c58068cc08</id>
<content type='text'>
Introduces a second (trivial) test for the python
bindings that searches for message ids and compares
the output with that of `notmuch search`.
</content>
</entry>
<entry>
<title>clean up "compare thread ids" python test</title>
<updated>2012-01-08T12:46:25Z</updated>
<author>
<name>Patrick Totzke</name>
<email>patricktotzke@googlemail.com</email>
</author>
<published>2012-01-02T14:51:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=aadf202dd57f71e93cd598a1c31bd6fb82b011f7'/>
<id>urn:sha1:aadf202dd57f71e93cd598a1c31bd6fb82b011f7</id>
<content type='text'>
This makes the test script open the database in READ_ONLY mode
and use the libraries own sorting methods instead of "sort".
</content>
</entry>
<entry>
<title>lib: call g_mime_init() from notmuch_database_open()</title>
<updated>2012-01-01T03:08:15Z</updated>
<author>
<name>Kazuo Teramoto</name>
<email>kaz.rag@gmail.com</email>
</author>
<published>2011-12-31T04:37:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=442d405ad301bd0bc9dc1d385c21f943ba743308'/>
<id>urn:sha1:442d405ad301bd0bc9dc1d385c21f943ba743308</id>
<content type='text'>
As reported in
id:"CAEbOPGyuHnz4BPtDutnTPUHcP3eYcRCRkXhYoJR43RUMw671+g@mail.gmail.com"
sometimes gmime tries to access a NULL pointer, e.g. g_mime_iconv_open()
tries to access iconv_cache that is NULL if g_mime_init() is not called.
This causes notmuch to segfault when calling gmime functions.

Calling g_mime_init() initializes iconv_cache and others variables needed
by gmime, making sure they are initialized when notmuch calls gmime
functions.

Test marked fix by db.
</content>
</entry>
<entry>
<title>test: add two new messages to corpus with iso-8859-1 encoding</title>
<updated>2012-01-01T03:04:01Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-01-01T02:15:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7da6733e890b913281afd5061cf5a648094a1eb4'/>
<id>urn:sha1:7da6733e890b913281afd5061cf5a648094a1eb4</id>
<content type='text'>
One is quoted printable, the other users 8 bit encoding. The latter
triggers a bug in the python bindings due to missing call to
g_mime_init. The corresponding test is marked broken in this commit.
</content>
</entry>
<entry>
<title>test: add a function to run Python tests</title>
<updated>2011-12-11T14:40:14Z</updated>
<author>
<name>Thomas Jost</name>
<email>schnouki@schnouki.net</email>
</author>
<published>2011-12-07T09:46:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2621f6cef19acc99745c389f5e324fea55f655d8'/>
<id>urn:sha1:2621f6cef19acc99745c389f5e324fea55f655d8</id>
<content type='text'>
The new test_python() function makes writing Python tests a little easier:
- it sets the environment variables as needed
- it redirects stdout to the OUTPUT file (like test_emacs()).

This commit also declares python as an external prereq.

The stdout redirection is required to avoid trouble when running commands like
"python 'script' | sort &gt; OUTPUT": in such a case, any error due to a missing
external prereq would be "swallowed" by sort, resulting to a failed test instead
of a skipped one.
</content>
</entry>
<entry>
<title>test/python: set LD_LIBRARY_PATH and PYTHONPATH to use local notmuch</title>
<updated>2011-12-06T03:06:50Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-12-06T03:06:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=07bb8b9e895541006eca88430925f1c6524c4708'/>
<id>urn:sha1:07bb8b9e895541006eca88430925f1c6524c4708</id>
<content type='text'>
Possibly this should be factored out into some kind of "run_python"
function.
</content>
</entry>
<entry>
<title>test: add tests for python bindings</title>
<updated>2011-12-05T22:06:48Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-12-05T01:50:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6cca3a5c16dac539db135920bc9ef9c5d237a1d5'/>
<id>urn:sha1:6cca3a5c16dac539db135920bc9ef9c5d237a1d5</id>
<content type='text'>
We start modestly, with a (slightly modified) test case from Kazuo
Teramoto. Originally it just made sure the bindings didn't crash; here
we check that by comparing the output with that of notmuch search.
</content>
</entry>
</feed>
