On Thu, Nov 18, 2021 at 10:01:17AM +0100, Sebastiaan Couwenberg wrote: > On 11/18/21 09:49, Matthias Klose wrote: > > On 11/18/21 06:51, Sebastiaan Couwenberg wrote: > > > On 11/16/21 14:23, Matthias Klose wrote: > > > > I'm planning to upload python3-defaults later tonight, adding 3.10 as a > > > > supported Python version. Packages are able to migrate on their own, there are > > > > no blockages introduced on other transitions. > > > > > > numpy rdeps (e.g. pyproj) are a bit problematic, they fail with the 3.10 as long > > > as numpy is not built with it yet. > > > > numpy is in stage6 of the transition. so please be a bit patient until all the > > binNMUs up to stage6 are built. > > There has been no communication about this transition outside this > bugreport, you should probably follow the example for perl transitions to > alert the developer base about the expected ImportError issues with the new > version until the rebuilds are completed. This Python transition is different from the Perl transitions. Python has multiple simultaneously supported versions, in this case 3.9 and 3.10. The transition involves rebuilding the packages with C extensions so that they carry the associated binary files compiled for both support Python versions. Any errors due to missing support in dependencies affect only people building Python packages. The default Python is still Python 3.9, so users using Python programs are not affected during this transition. Perl, on the other hand, has only a single version at the archive at any time. This is why during the Perl transition, it's possible that users running Perl programs are affected by missing C extensions during the time it takes to rebuild all packages for the new Perl version.
Attachment:
signature.asc
Description: PGP signature