From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: python-future missing python 3.8 and 3.9 support
Date: Tue, 3 May 2022 23:15:38 +0100 [thread overview]
Message-ID: <7dca3df9-89d5-c69d-36b8-8b10223813f7@dronecode.org.uk> (raw)
In-Reply-To: <525af389-ce91-a079-617c-0311c54585b2@seznam.cz>
On 03/05/2022 21:25, Libor Ukropec wrote:
> Hello Jon, maintainers,
>
> who is now the maintainer of the python-future - Jon Turney?
Yes, it seems to be me, I don't know quite why though...
> The python-future supports only python 2.7, 3.6 and 3.7 and these are
> basically obsolete. I'd like to add support for 3.8 and 3.9 - it should
> allow me to support `duplicity` package with the latest python (3.9).
>
> PYTHON_WHEEL_VERSIONS variable should help. Can I kindly ask someone for
> the package update?
>
> Thank you and regards,
> Libor
>
> diff --git a/python-future.cygport b/python-future.cygport
> index 3151b74..6f586ae 100644
> --- a/python-future.cygport
> +++ b/python-future.cygport
> @@ -3,6 +3,7 @@ VERSION=0.18.2
> RELEASE=1
> ARCH=noarch
>
> +PYTHON_WHEEL_VERSIONS="2.7:3.6:3.7:3.8:3.9"
> inherit python-wheel
>
> HOMEPAGE="http://python-future.org/"
> @@ -20,3 +21,4 @@ src_install() {
> }
>
> python36_future_CONTENTS+=" usr/bin/*"
> +python37_future_CONTENTS+=" usr/bin/*"
>
Thanks. I rebuilt python-future with this change.
next prev parent reply other threads:[~2022-05-03 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 20:25 Libor Ukropec
2022-05-03 22:15 ` Jon Turney [this message]
2022-05-04 23:04 ` Libor Ukropec
2022-05-08 12:43 ` Jon Turney
2022-05-08 15:25 ` Libor Ukropec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7dca3df9-89d5-c69d-36b8-8b10223813f7@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/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.
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).