Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #16237 > unrolled thread

Python3.12 and a half

Back to article view | Back to linux.debian.maint.python

Contents

  Python3.12 and a half Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-08-22 21:40 +0200
    Re: Python3.12 and a half Matthias Klose <doko@debian.org> - 2024-08-23 10:00 +0200
      Re: Python3.12 and a half Julian Gilbey <julian@d-and-j.net> - 2024-08-23 10:20 +0200
        Re: Python3.12 and a half Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-23 10:30 +0200
        Re: Python3.12 and a half Louis-Philippe Véronneau <pollo@debian.org> - 2024-09-02 02:20 +0200
    Re: Python3.12 and a half Antonio Terceiro <terceiro@debian.org> - 2024-08-23 12:30 +0200
      Re: Python3.12 and a half Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-08-23 14:40 +0200
    [2to3 and fissix] Re: Python3.12 and a half  Nicholas D Steeves <sten@debian.org> - 2024-09-11 15:30 +0200
      Re: [2to3 and fissix] Re: Python3.12 and a half Alexandre Detiste <alexandre.detiste@gmail.com> - 2024-09-13 12:50 +0200

#16237 — Python3.12 and a half

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+python@tracker.debian.org>
Changed-By: Antonio Terceiro <terceiro@debian.org>
Changes:
 slimit (0.8.1-7) unstable; urgency=medium
 .
   * Team upload.
   * Add build dependency on python3-lib2to3 (Closes: #1076961)

[toc] | [next] | [standalone]

#16238

On 22.08.24 21:37, Alexandre Detiste wrote:
> 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

[toc] | [prev] | [next] | [standalone]

#16239

On Fri, Aug 23, 2024 at 09:55:17AM +0200, Matthias Klose wrote:
> On 22.08.24 21:37, Alexandre Detiste wrote:
> > 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

[toc] | [prev] | [next] | [standalone]

#16240

Am 23.08.24 um 10:19 schrieb 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/

-- 
Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#16249

[Multipart message — attachments visible in raw view] — view raw

On 2024-08-23 4 h 19 a.m., Julian Gilbey wrote:
> On Fri, Aug 23, 2024 at 09:55:17AM +0200, Matthias Klose wrote:
>> On 22.08.24 21:37, Alexandre Detiste wrote:
>>> 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
   ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
   ⠈⠳⣄

[toc] | [prev] | [next] | [standalone]

#16241

[Multipart message — attachments visible in raw view] — view raw

On Thu, Aug 22, 2024 at 09:37:07PM +0200, Alexandre Detiste wrote:
> 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.

[toc] | [prev] | [next] | [standalone]

#16242

Thank you, less-is-more it seems.

Le ven. 23 août 2024 à 12:27, Antonio Terceiro <terceiro@debian.org> a écrit :
> 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.

[toc] | [prev] | [next] | [standalone]

#16271 — [2to3 and fissix] Re: Python3.12 and a half

[Multipart message — attachments visible in raw view] — view raw

Alexandre Detiste <alexandre.detiste@gmail.com> writes:

> 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

[toc] | [prev] | [next] | [standalone]

#16279 — Re: [2to3 and fissix] Re: Python3.12 and a half

Le mer. 11 sept. 2024 à 15:21, Nicholas D Steeves <sten@debian.org> a écrit :
>
> Alexandre Detiste <alexandre.detiste@gmail.com> writes:
> 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.

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web