From: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: Python3 cffi bindings
Date: Wed, 04 Dec 2019 22:18:41 +0200 [thread overview]
Message-ID: <m2pnh3x2se.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87a78vu5x2.fsf@tethera.net>
On Sat, Nov 16 2019, David Bremner wrote:
> Gaute Hope <eg@gaute.vetsj.com> writes:
>
>>
>> By the way, it does not seem that the API is very far from the
>> previous python API. If it is close enough, perhaps it is possible to
>> get away with a bug version bump in the bindings rather than creating
>> a new package. I understand the need for a new package, but it would
>> be nice if we could avoid the future confusion of two python binding
>> packages (if at all possible).
>>
>
> I'm not in a good position to judge how similar the APIs are. It does
> seem like there are at least some breaking changes, and we usually try
> to make things smooth for people upgrading by deprecating interfaces
> before removing them completely. On the other hand our previous concern
> for supporting python pre 3.6 (I think. Maybe 3.5?) seems less and less
> worrying (except maybe for people using old CentOS like things).
Currently such a recent Linux distribution as Ubuntu 16.04 LTS is not new
enough to be used as is when compiling latest notmuch from git (or 0.29),
as GMIME 3.0 is required (Ubuntu 16.04 ships GMIME 2.6 and Python 3.5).
GMIME 2.6 was pretty easy to compile, GMIME 3 is a bit harder...
Ubuntu 16.04 LTS ships python 3.5 -- and compiling later Pythons is easier
than GMIME 3 (done both, GMIME 3 on CentOS 6, Python 3.7 on CentOS 7).
So, IMO not supporting python pre 3.6 is fine, as we already reguire gmime 3
and probably soon xapian 1.4 -- distros that ship gmime3 most probably
already ship python 3.6...
Tomi
>
> d
next prev parent reply other threads:[~2019-12-04 20:18 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
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 [this message]
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=m2pnh3x2se.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--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).