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


Groups > linux.debian.maint.python > #14798

Re: Python 3.11 for bookworm?

From Thomas Goirand <zigo@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Python 3.11 for bookworm?
Date 2023-01-05 14:00 +0100
Message-ID <FKy0F-fKED-3@gated-at.bofh.it> (permalink)
References <FFc0N-cezl-9@gated-at.bofh.it> <FFhtv-chWO-1@gated-at.bofh.it> <FFizf-cix6-1@gated-at.bofh.it> <FHsXv-dKHT-1@gated-at.bofh.it> <FIjSa-eivi-11@gated-at.bofh.it>
Organization Debian

Show all headers | View raw


Hi Andreas,

On 12/30/22 10:22, Andreas Tille wrote:
> True, I remember the DebConf Python BoF.  My memory tells me that the
> plan was to keep 3.10 as default.  Thus Python 3.11 would be really a
> surprise.  From a maintainers team with lots of Python packages that
> will need heavy work I can't say I'd be happy about a "migrate and see
> what might happen afterwards" strategy as it was proposed here.  We have
> lots to do even without such an experiment.

This has since already been discussed here: the final decision was to 
"at least try 3.11", which is exactly what we're doing.

>   
>> Well, that's not the first time we are trying to push the latest interpreter
>> close to a release.
> 
> The fact that we did so before does not make the idea better.
> 
>> I also very much would appreciate help on these (which all look like
>> probably related to py3.11):
>>
>> #1026524 ironic-inspector: FTBFS: AttributeError: '_thread.RLock' object has
>> no attribute 'is_locked'
>> #1026547 python-pypowervm: FTBFS: AssertionError: Expected 'warn' to be
>> called once. Called 2 times.
>> #1026549 python-pytest-xprocess: FTBFS: tests failed
>> #1026591 cinder: FTBFS: make[1]: pyversions: No such file or directory
>> #1026595 python-murano-pkg-check: FTBFS: TypeError: load_all() missing 1
>> required positional argument: 'Loader'
>> #1026610 horizon: FTBFS: tests failed
>> #1026691 bandit: FTBFS: TypeError: load() missing 1 required positional
>> argument: 'Loader'
>> #1026693 cloudkitty: FTBFS: touch: cannot touch '/<<PKGBUILDDIR>>/debian/cloudkitty-doc/usr/share/doc/cloudkitty-doc/html/_static/toggle.js':
>> No such file or directory
>> #1026702 python-cursive: FTBFS: AttributeError: '_RSAPrivateKey' object has
>> no attribute 'signer'
>> #1026705 python-pecan: FTBFS: E AttributeError: 'code' object has no
>> attribute 'co_endlinetable'
>> #1026707 jenkins-job-builder: FTBFS: E: pybuild pybuild:386: test: plugin
>> custom failed with: exit code=1: PYTHON=python3.10 stestr run

FYI, I'm down with only 2 major bugs (I don't mind much if the other 3 
RC bugs push the 3 affected packages away from the release, it's just a 
"would be nice" thing ATM):

#1026524 ironic-inspector: FTBFS: AttributeError: '_thread.RLock' object 
has no attribute 'is_locked'
#1026591 cinder: FTBFS: make[1]: pyversions: No such file or directory

The first one also appears in Python 3.10.9, but seems not present in 
Python 3.10.6, as per a discussion with upstream on IRC. It looks like 
the default threading thingy has changed a little bit, leading to 
this... I know already how to fix the actual executed code, but this 
leaves some wrong tests (assert called), so I'm waiting to see if 
upstream can do better than me.

For the Cinder bug, it looks like a test-only issue, which upstream is 
already working on. Worst case: blacklist these 250 failing tests, which 
is better than what it sounds (ie: just like Ironic, the actual 
production code is ok...).

> If I would create a list mine whould be way longer.

Please share it in this list!

> We are constantly beaten by removal from testing warnings
> even with Python3.11 as an option and sometimes we simply need to remove
> that option as a temporary means for bookworm.

Same over here. It's finally looking good for me after 2 months of heavy 
efforts.

> No better solution but better timing which means after bookworm release.

I've read *many* people saying it would be disappointing for them to see 
their package removed because of Python 3.11. Well, please consider that 
it would also be very disappointing to *not* have Python 3.11 for those 
who managed constantly fix issues for it.

The timing was exactly what was discussed during Debconf: it's very 
annoying that this year, upstream Python release was one month late... 
we're only trying to deal with it.

Cheers,

Thomas Goirand (zigo)

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Python 3.11 for bookworm? Matthias Klose <doko@ubuntu.com> - 2022-12-21 19:30 +0100
  Re: Python 3.11 for bookworm? Sandro Tosi <morph@debian.org> - 2022-12-22 01:20 +0100
    Re: Python 3.11 for bookworm? Nicholas D Steeves <sten@debian.org> - 2022-12-22 02:30 +0100
      Re: Python 3.11 for bookworm? "M. Zhou" <lumin@debian.org> - 2022-12-22 06:10 +0100
      Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2022-12-28 02:00 +0100
        Re: Python 3.11 for bookworm? Andreas Tille <andreas@an3as.eu> - 2022-12-30 10:30 +0100
          Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2023-01-05 14:00 +0100
            Re: Python 3.11 for bookworm? Andreas Tille <andreas@an3as.eu> - 2023-01-07 09:10 +0100
              Re: Python 3.11 for bookworm? Andrius Merkys <merkys@debian.org> - 2023-01-07 09:30 +0100
                Re: Python 3.11 for bookworm? Andrius Merkys <merkys@debian.org> - 2023-01-09 16:50 +0100
              Re: Python 3.11 for bookworm? Andreas Tille <andreas@an3as.eu> - 2023-01-16 17:30 +0100
                Re: Python 3.11 for bookworm? Thomas Goirand <zigo@debian.org> - 2023-01-17 01:10 +0100
                Re: Python 3.11 for bookworm? Andreas Tille <tille@debian.org> - 2023-01-17 07:50 +0100
            Re: Python 3.11 for bookworm? Étienne Mollier <emollier@emlwks999.eu> - 2023-01-10 22:50 +0100
    Re: Python 3.11 for bookworm? Stefano Rivera <stefanor@debian.org> - 2022-12-22 13:50 +0100
      Re: Python 3.11 for bookworm? Timo Röhling <roehling@debian.org> - 2022-12-22 14:00 +0100
        Re: Python 3.11 for bookworm? Stefano Rivera <stefanor@debian.org> - 2022-12-22 19:50 +0100
          Re: Python 3.11 for bookworm? "M. Zhou" <lumin@debian.org> - 2022-12-23 00:30 +0100
            Re: Python 3.11 for bookworm? "M. Zhou" <lumin@debian.org> - 2022-12-23 00:40 +0100
          Re: Python 3.11 for bookworm? Graham Inggs <ginggs@debian.org> - 2022-12-26 21:30 +0100
  Re: Python 3.11 for bookworm? Graham Inggs <ginggs@debian.org> - 2022-12-26 21:50 +0100

csiph-web