Python3.12 and a half

[Alexandre Detiste]

Hi,

Would it be possible to remove 2to3 from Python3.12 without waiting for 3.13 ?

I see in the meantime a new usage was brought back.

I'll check if this "slimit" package can be easily switched to python3-fissix;
which is a 2to3 fork that is already used to keep python3-nose
artificially alive.

Upstream doesn't have the nicest ward about this module;
I guess nobody will miss it by now.

https://bugs.python.org/issue40360
"Now we just have to remember to actually remove the damn thing in 3.13 😂"

Greetings
---

Date: Wed, 21 Aug 2024 15:12:40 -0300
Version: 0.8.1-7
Urgency: medium
Maintainer: Debian Python Team <team+***@tracker.debian.org>
Changed-By: Antonio Terceiro <***@debian.org>
Changes:
slimit (0.8.1-7) unstable; urgency=medium
.
* Team upload.
* Add build dependency on python3-lib2to3 (Closes: #1076961)

[Matthias Klose]

Post by Alexandre Detiste
Hi,
Would it be possible to remove 2to3 from Python3.12 without waiting for 3.13 ?
I see in the meantime a new usage was brought back.
I'll check if this "slimit" package can be easily switched to python3-fissix;
which is a 2to3 fork that is already used to keep python3-nose
artificially alive.

I'd like to avoid addressing a single module. 3.13 has a whole bunch of
modules that are removed in the standard library.

What's the status of filing bug reports for all these removed modules?

Matthias

[Julian Gilbey]

Post by Matthias Klose

Post by Alexandre Detiste
Hi,
Would it be possible to remove 2to3 from Python3.12 without waiting for 3.13 ?
I see in the meantime a new usage was brought back.
I'll check if this "slimit" package can be easily switched to python3-fissix;
which is a 2to3 fork that is already used to keep python3-nose
artificially alive.

I'd like to avoid addressing a single module. 3.13 has a whole bunch of
modules that are removed in the standard library.
What's the status of filing bug reports for all these removed modules?
Matthias

Lintian does do a check for them: uses-deprecated-python-stdlib
but beware of false positives, in particular for uu and crypt; see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077324 (which is
now pending an upload). (There used to be a website
lintian.debian.org where you could search reports by tag, but that
doesn't seem to exist any more, and I haven't had any luck searching
with UDD.)

Best wishes,

Julian

[Carsten Schoenert]

Post by Julian Gilbey
Lintian does do a check for them: uses-deprecated-python-stdlib
but beware of false positives, in particular for uu and crypt; see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077324 (which is
now pending an upload). (There used to be a website
lintian.debian.org where you could search reports by tag, but that
doesn't seem to exist any more, and I haven't had any luck searching
with UDD.)

There was recently a longish discussion about the currently not existing
website about the Lintian tags and affected packages on debian-devel.

TLDR
You can use this URL in between time to get this old service back.

https://lintian.club1.fr/

[Louis-Philippe Véronneau]

Post by Julian Gilbey

Post by Matthias Klose

Post by Alexandre Detiste
Hi,
Would it be possible to remove 2to3 from Python3.12 without waiting for 3.13 ?
I see in the meantime a new usage was brought back.
I'll check if this "slimit" package can be easily switched to python3-fissix;
which is a 2to3 fork that is already used to keep python3-nose
artificially alive.

I'd like to avoid addressing a single module. 3.13 has a whole bunch of
modules that are removed in the standard library.
What's the status of filing bug reports for all these removed modules?
Matthias

Lintian does do a check for them: uses-deprecated-python-stdlib
but beware of false positives, in particular for uu and crypt; see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077324 (which is
now pending an upload). (There used to be a website
lintian.debian.org where you could search reports by tag, but that
doesn't seem to exist any more, and I haven't had any luck searching
with UDD.)

Hi,

This is probably what you were looking for:

https://udd.debian.org/lintian-tag.cgi

More specifically:

https://udd.debian.org/lintian-tag.cgi?tag=uses-deprecated-python-stdlib

As for #1077324, in theory I just pushed the fix to the buildds. In
practice, this is my first Lintian release, so we'll see how that goes :P

When/if 2.118.1 gets in the archive, I'll ping Luca to update UDD's
lintian version.

Cheers,

--
⢀⣎⠟⠻⢶⣊⠀
⣟⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ ***@debian.org / veronneau.org
⠈⠳⣄

[Antonio Terceiro]

Post by Alexandre Detiste
Hi,
Would it be possible to remove 2to3 from Python3.12 without waiting for 3.13 ?
I see in the meantime a new usage was brought back.
I'll check if this "slimit" package can be easily switched to python3-fissix;
which is a 2to3 fork that is already used to keep python3-nose
artificially alive.

FWIW I tried just dropping the check for 2to3, and all the tests for slimit
itself passed. Rebuilding reverse build dependencies and autopkgtest for
reverse dependencies also worked.

So I uploaded a new version with that change.

[Alexandre Detiste]

Thank you, less-is-more it seems.

Post by Antonio Terceiro
FWIW I tried just dropping the check for 2to3, and all the tests for slimit
itself passed. Rebuilding reverse build dependencies and autopkgtest for
reverse dependencies also worked.
So I uploaded a new version with that change.

[Nicholas D Steeves]

Post by Alexandre Detiste
Hi,
Would it be possible to remove 2to3 from Python3.12 without waiting for 3.13 ?
I see in the meantime a new usage was brought back.
I'll check if this "slimit" package can be easily switched to python3-fissix;
which is a 2to3 fork that is already used to keep python3-nose
artificially alive.

For the record, python3-fissix is a backport of the latest available
2to3, not a fork. I communicated with upstream about its future a
couple of years ago, and the long-term plan at that time was that fissix
would either:

1. Cease to exist when 2to3 was eventually dropped (both were planned
even back then), or else
2. Possibly migrate to something else but maintain legacy interfaces
3. Someone else actually forks 2to3 from Python 3.12, and fissix
begins to depend on that fork.

Has anyone heard anything about the second or third cases?

Regards,
Nicholas

[Alexandre Detiste]

Post by Nicholas D Steeves
For the record, python3-fissix is a backport of the latest available
2to3, not a fork. I communicated with upstream about its future a
couple of years ago, and the long-term plan at that time was that fissix
1. Cease to exist when 2to3 was eventually dropped (both were planned
even back then), or else
2. Possibly migrate to something else but maintain legacy interfaces
3. Someone else actually forks 2to3 from Python 3.12, and fissix
begins to depend on that fork.

I see that the only package requiring "modernize"
has dropend it's usage lately:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077959

moderinze depends on fissix.

The only two other packages needing fissix are
"python-untokenize" for one test
and "nose" that should go away.

After this I don't know what will happen with fissix.

Greetings