Re: New Python bindings (was: Crash with Python bindings)

Subject: Re: New Python bindings (was: Crash with Python bindings)

Date: Thu, 29 Mar 2018 09:37:08 +1100



From: Brian May

David Bremner <> writes:

> We tried this before, and it didn't work out very well. Bindings tend to
> depend on a strict matching of versions with the underlying library, so
> distributing them seperately doesn't really make sense to me. You need
> the underlying libraries, so why not get the matching bindings from the
> same place?  We found that the situation was exacerbated by the fact
> that no-one cared about updating the bindings on pypi.

I believe that is the purpose of Python Wheels.

pypi is the defecto standard for distributing Python code for use in
Python applications. It means packages that use notmuch just need to
list it as a dependancy in 'requirements.txt' and a 'pip install -r
requirements.txt' will install everything required (if inside a
virtualenv no root access required even).

There are also various solutions to get automatic deploys to pypi, for
example through travis:

Unfortunately, I think many people will not even consider using a python
library unless it has up-to-date bindings available on pypi.
Brian May <>
notmuch mailing list