python-future missing python 3.8 and 3.9 support

python-future missing python 3.8 and 3.9 support

[Libor Ukropec]

Hello Jon, maintainers,

who is now the maintainer of the python-future - Jon Turney?

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/*"

Re: python-future missing python 3.8 and 3.9 support

[Jon Turney]

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.

Re: python-future missing python 3.8 and 3.9 support

[Libor Ukropec]

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

Re: python-future missing python 3.8 and 3.9 support

[Jon Turney]

On 05/05/2022 00:04, Libor Ukropec wrote:
> 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.

Thanks. I've given you maintainership of python-future, although it 
seems pretty mature, so hopefully won't require updating.

>>> 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!

Yeah, the situation is not ideal, and ideally something would be done to 
improve this situation, perhaps so we can automatically rebuild all the 
python packages for 3.9 or 3.10 when we get to that, but ... SHTDI...

Re: python-future missing python 3.8 and 3.9 support

[Libor Ukropec]

Dne 08.05.2022 v 14:43 Jon Turney napsal(a):
> On 05/05/2022 00:04, Libor Ukropec wrote:
>> 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.
> 
> Thanks. I've given you maintainership of python-future, although it 
> seems pretty mature, so hopefully won't require updating.
I am a cygwin user for ages and I'll be glad if I am able to give 
something back to this community.

> 
>>>> 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!
> 
> Yeah, the situation is not ideal, and ideally something would be done to 
> improve this situation, perhaps so we can automatically rebuild all the 
> python packages for 3.9 or 3.10 when we get to that, but ... SHTDI...
> 
Well, if this can be automated that will be cool. If not, I'm ready to help.