From: Floris Bruynooghe <flub@devork.be>
To: David Bremner <david@tethera.net>,
Ralph Seichter <abbot@monksofcool.net>,
notmuch@notmuchmail.org
Subject: Re: Python 3.x bindings support which versions, exactly?
Date: Mon, 25 May 2020 23:25:42 +0200 [thread overview]
Message-ID: <874ks3wvu1.fsf@powell.devork.be> (raw)
In-Reply-To: <871rn95dys.fsf@tethera.net>
On Sun 24 May 2020 at 16:29 -0300, David Bremner wrote:
> Ralph Seichter <abbot@monksofcool.net> writes:
>
>> Hello,
>>
>> having examined the source code, I assume that Notmuch's Python bindings
>> should support Python 3.x for any given 'x'. However, reading the Travis
>> logs at https://travis-ci.org/notmuch/notmuch and .travis.yml, the CI
>> tests apparently run on Ubuntu 18.04 and use only Python 3.6.
>>
>> While I hope there won't be any problems with Python 3.7, 3.8 and 3.9,
>> I wanted to ask here first if anybody has tested this yet?
>
> the old (modulename = notmuch) bindings actually do have memory
> management issues with python > 3.6 (maybe also with 3.6). The new
> bindings (modulename= notmuch2) should work with any python recent
> 3.x.
In tox.ini the earliest version is 3.5 and if memory serves me right
there's a reasonably good reason for that. I think the notmuch2
bindings use some features not yet present in 3.4. But anything >= 3.5
should be supported and if not a bug. I guess tox.ini should be updated
with 3.8 sometime :)
Cheers,
Floris
next prev parent reply other threads:[~2020-05-25 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 18:52 Python 3.x bindings support which versions, exactly? Ralph Seichter
2020-05-24 19:29 ` David Bremner
2020-05-24 20:24 ` Ralph Seichter
2020-05-24 21:46 ` David Bremner
2020-05-24 22:06 ` Ralph Seichter
2020-05-25 21:25 ` Floris Bruynooghe [this message]
2020-05-25 21:41 ` Tomi Ollila
2020-06-05 20:12 ` Floris Bruynooghe
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=874ks3wvu1.fsf@powell.devork.be \
--to=flub@devork.be \
--cc=abbot@monksofcool.net \
--cc=david@tethera.net \
--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).