notmuch/bindings/python-cffi/notmuch2/_message.py, branch 0.39_rc3thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.39_rc32025-03-14T00:18:15Zbindings/python-cffi: fix docstring for message.header()2025-03-14T00:18:15ZMichael J Grubergit@grubix.eu2025-03-04T12:39:43Zurn:sha1:5802f5d6269172222a6fccf5908eae833014917b
The cffi bindings raise a LookupError in case a header is not present.
Adjust the docstring to say so.
The legacy bindings behaved differently, and this is one of the things
to be aware of when migrating to the cffi bindings.
python: Fix message ID docstring2025-02-28T15:31:55ZFloris Bruynoogheflub@devork.be2025-02-24T20:08:19Zurn:sha1:ed29a9c37ec382fc2d5b1d1ecc1f1fb28a6769c6
The messageidb attribute does not exist. The returned BinString type
already allows use as both strings and binary. Presumably this was
written before that type was adopted.
python: fix documentation typo2025-02-22T10:59:48ZDavid Bremnerdavid@tethera.net2025-02-15T19:27:51Zurn:sha1:9782c8651192c1496541bd8949b7991c41528b3f
The method is actually called 'getall'.
fix segfaults in Python cFFI API and add tests2025-02-07T16:13:16ZLars Kotthofflars@larsko.org2025-02-06T02:52:51Zurn:sha1:9c1f6cf746725af7bbbb66e746c5d694723ac0eb
Several iterators in the Python cFFI API destroyed the objects they iterated
over too early (when the iterator was exhausted), causing subsequent segfaults
in common cases like creating a list from the iterator. This patch fixes the
segfaults and add tests to ensure that they don't happen again.
bindings/python-cffi: fix docstring2022-07-05T10:34:25ZDavid Bremnerdavid@tethera.net2022-07-03T20:26:46Zurn:sha1:db44af75ad5a79b3fd5ecad93fe95195ef175ebd
the method Database.get_message does exist any more (if it ever
did). This makes the docstring unhelpful as an example.
Merge branch 'release'2022-01-09T13:20:56ZDavid Bremnerdavid@tethera.net2022-01-09T13:20:56Zurn:sha1:22e04ed01acc115b7fb25b60231014f585f11c4apython-cffi: returned OwnedMessage objects from Message.replies2022-01-08T20:29:41ZDavid Bremnerdavid@tethera.net2022-01-08T14:03:16Zurn:sha1:9e7ea628e6bddbd7345d053a3daf14af74896cc2
If we return regular Message objects, python will try to destroy them,
and the underlying notmuch object, causing e.g. the crash [1].
[1]: id:87sfu6utxg.fsf@tethera.net
bindings/python-cffi: add matched property to message objects2022-01-01T15:48:40ZDavid Bremnerdavid@tethera.net2022-01-01T14:36:43Zurn:sha1:9cc026f3daaa7731527787f8c7e729c0a08c456c
Existing users of the legacy python bindings use
message.get_flags(Message.FLAG.MATCH) to determine which messages in a
thread matched. Since the bindings don't provide get_flags anymore,
they should provide a property analogous to the existing "excluded"
property.
Fix typos2020-08-10T00:14:36ZJonas Bernoullijonas@bernoul.li2020-08-08T11:49:55Zurn:sha1:6c84dee53193a78cf797b44d3febcc14488ea6b1Make messages returned by Thread objects owned2020-06-16T11:02:02ZFloris Bruynoogheflub@devork.be2020-06-15T20:58:50Zurn:sha1:2d895a0119b423b117d10e890c9e0eb5d2a9cdf8
This reverses the logic of StandaloneMessage to instead create a
OwnedMessage. Only the Thread class allows retrieving messages more
then once so it can explicitly create such messages.
The added test fails with SIGABRT without the fix for the message
re-use in threads being present.