notmuch/bindings/python-cffi/tests/test_thread.py, branch 0.38.1 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.38.1 2022-01-09T23:34:58Z Merge tag '0.34.3' 2022-01-09T23:34:58Z David Bremner david@tethera.net 2022-01-09T23:34:58Z urn:sha1:63d3b2b5cf8702b5fecea77392ce46f8a8249175 notmuch 0.34.3 release bindings/python-cffi: search for config by default 2022-01-09T19:16:51Z David Bremner david@tethera.net 2022-01-08T21:21:43Z urn:sha1:8b737af28bc377db3e661a5744f3b7479b7ce485 The previous (pre-0.34.2) constructor searched for a config file but only if the database path was not specified, and only to retrieve database.path. Neither of the available options (CONFIG.SEARCH or CONFIG.NONE) matches this semantics exactly, but CONFIG.SEARCH causes less breakage for people who relied on the old behaviour to set their database.path [1]. Since it also seems like the friendlier option in the long run, this commit switches to CONFIG.SEARCH as default. This requires a certain amount of updating the pytest tests, but most users will actually have a config file, unlike the test environment. [1]: id:87fsqijx7u.fsf@metapensiero.it bindings/python-cffi: add matched property to message objects 2022-01-01T15:48:40Z David Bremner david@tethera.net 2022-01-01T14:36:43Z urn: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. Rename package to notmuch2 2019-12-03T12:12:30Z Floris Bruynooghe flub@devork.be 2019-11-17T16:41:35Z urn:sha1:e2df30f7a98f91543d0b3561dbb366eb4b3d812c This is based on a previous discussion on the list where this was more or less seen as the least-bad option. Introduce CFFI-based python bindings 2019-12-03T12:12:30Z Floris Bruynooghe flub@google.com 2019-10-08T21:03:12Z urn:sha1:83c2d158983875bf77a9b7662894df585b61741c This introduces CFFI-based Python3-only bindings. The bindings aim at: - Better performance on pypy - Easier to use Python-C interface - More "pythonic" - The API should not allow invalid operations - Use native object protocol where possible - Memory safety; whatever you do from python, it should not coredump.