notmuch/bindings/python-cffi/setup.py, branch 0.40

bindings/python: strip ~ from python version

2025-02-22T11:10:13Z

Inspired by a suggestion of Xiyue Deng, this change ensures that the python bindings have a version that recent setuptools is happy with. This will have the unfortunate side effect of the python view of the version number differing from the rest of notmuch for the pre-releases. The alternative would be to transform the version numbers for the Debian packages for the pre-releases, as there is now no version scheme that works for both, since setuptools started rejecting versions with "~" in them. If we decide to go the latter way in the future, this change is easy to revert.

python-cffi: fix out-of-tree build

2021-12-05T13:08:48Z

The main idea is to replace the hack of copying version.txt into the bindings source with a generated _notmuch_config.py file. This will mean that the bindings only build after configuring and building notmuch itself. Given those constraints, "pip install ." should work.

Rename version to version.txt

2020-10-30T19:14:24Z

Building Notmuch on macOS is known to cause problems because the Notmuch distribution archive contains two files named "version". These names clash with the header as defined in C++20. Therefore, the existing naming will likely become a problem on other platforms as well, once compilers adopt the new standard. Signed-off-by: Ralph Seichter Amended-by: db s/keyword/header/ in commit message.

bindings/python-cffi: copy version file into bindings dir

2020-07-03T09:38:55Z

Attempt to avoid breaking "pip install ." As far as I can tell, we need to have a copy (not just a relative symlink) of the version file.

python-cffi: read version from notmuch version file

2020-06-19T10:01:13Z

This keeps it in sync with the main notmuch version which is less confusing to users.

Rename package to notmuch2

2019-12-03T12:12:30Z

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

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.