From: David Bremner <david@tethera.net>
To: Floris Bruynooghe <flub@devork.be>, notmuch@notmuchmail.org
Subject: Re: Python3 cffi bindings
Date: Mon, 14 Oct 2019 09:40:09 -0300 [thread overview]
Message-ID: <8736fvbivq.fsf@tethera.net> (raw)
In-Reply-To: <20191008210312.20685-1-flub@devork.be>
Floris Bruynooghe <flub@devork.be> 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.
next prev parent reply other threads:[~2019-10-14 12:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 21:03 Python3 cffi bindings Floris Bruynooghe
2019-10-08 21:03 ` [PATCH] Introduce CFFI-based python bindings Floris Bruynooghe
2019-10-08 22:24 ` Python3 cffi bindings David Bremner
2019-10-09 18:34 ` Floris Bruynooghe
2019-10-14 12:40 ` David Bremner [this message]
2019-10-14 12:42 ` David Bremner
2019-10-17 17:35 ` Floris Bruynooghe
2019-10-20 12:22 ` David Bremner
2019-10-22 16:32 ` David Bremner
2019-10-25 9:57 ` Floris Bruynooghe
2019-11-04 10:27 ` Gaute Hope
2019-11-16 16:44 ` David Bremner
2019-12-04 20:18 ` Tomi Ollila
2019-11-17 17:14 ` Floris Bruynooghe
2019-11-17 18:01 ` Gaute Hope
2020-10-08 8:13 ` Gaute Hope
2020-10-14 20:23 ` Floris Bruynooghe
2020-10-16 7:19 ` Gaute Hope
2020-10-16 7:24 ` Gaute Hope
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736fvbivq.fsf@tethera.net \
--to=david@tethera.net \
--cc=flub@devork.be \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).