Re: Python3 cffi bindings

2019-10-14 Thread David Bremner
David Bremner  writes:

> The shim in
> T391-python-cffi.sh doesn't work for me, it doesn't manage to set
> PYTHONPATH so that notdb is importable.

I should have mentioned that if I manually set python path with
something like

$ PYTHONPATH=`pwd`/build/lib.linux-x86_64-3.7:$PYTHONPATH pytest-3

it works OK.  Is there a simple/reliable way of calculating the path
lib.linux-x86_64-3.7?

d
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Re: Python3 cffi bindings

2019-10-14 Thread David Bremner
Floris Bruynooghe  writes:

> IIRC this probably wants to be renamed to "notmuch2" instead of
> "notdb".  Otherwise I'm pretty sure this doesn't cover all the
> current features either.

Yes, I think notmuch2 was the least disliked suggestion. 

> So maybe this can be used as a start to figure out how to merge
> this if there's still an interest in this.

I'm interested. The blocker for me at the moment is getting the tests
working without tox / venvs.  I'm hoping we can test with the system
python and the built, but not installed module. I guess we need to build
it so that the C extension part is loaded. The shim in
T391-python-cffi.sh doesn't work for me, it doesn't manage to set
PYTHONPATH so that notdb is importable.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch