public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: Re: python-future missing python 3.8 and 3.9 support
Date: Thu, 5 May 2022 01:04:34 +0200	[thread overview]
Message-ID: <1a005441-e982-1163-4bc0-f27bf3925b20@seznam.cz> (raw)
In-Reply-To: <7dca3df9-89d5-c69d-36b8-8b10223813f7@dronecode.org.uk>

Dne 04.05.2022 v 0:15 Jon Turney napsal(a):
> 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...
Hello Jon,
in this case if you want to, I can take over the responsibility for this 
package, just let me know.

> 
>> 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 
 >>...
> 
> Thanks.  I rebuilt python-future with this change.
That was quick, thank you.

Unfortunately because of the dependency hell (python paramiko => nacl, 
and may be others) I cannot use the Python 3.9, still your work enables 
me to use at least the Python 3.8 (where all dependencies are resolved), 
which is great!


Regards,
Libor



  reply	other threads:[~2022-05-04 23:04 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
2022-05-04 23:04   ` Libor Ukropec [this message]
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=1a005441-e982-1163-4bc0-f27bf3925b20@seznam.cz \
    --to=ace@seznam.cz \
    --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).