Adding Python 3.8 as a supported Python3 version
This weekend, I am planning to upload python3-defaults, adding python3.8 as a
supported Python3 version. This may introduce some churn in unstable until the
basic binNMUs are available as well.
Details for the addition can be found at [1], known issues and patches are filed
[2]. There was no test rebuild in Debian itself, but the addition was made in
the current Ubuntu development series. Things look good, and from my point of
view don't block any unrelated transition work. python3-defaults will get a RC
issue to stay in unstable until the packages build-depending on python3-all-dev
are built, and after doing a test rebuild with the two supported Python3
versions. Earlier test rebuilds don't make sense.
There are a few packages, where the upstream versions used in Ubuntu diverge
from the ones currently in unstable (not naming those already updated in
unstable by the DPMT):
- hypothesis #942693, not sure if this is really needed,
the testsuite stack might be fixed by the new pluggy
version as well.
- python-xarray #944044. 1.4 is already broken with Python 3.7. For
Ubuntu I fell back to 1.2.1. 1.2.3 might work as well, still seeing
one or two test failures.
- Using numpy from experimental, and only building the Python2 numpy
packages from the python-numpy source.
- Using python-scipy from experimental, building the Python3 packages,
and renaming the python-scipy package to python2-scipy, only building
the Python2 packages.
- matplotlib and pandas don't have Python2 packages in Ubuntu
anymore, so I can't tell much what is needed here. Pandas needs
a new upstream for 3.8.
Packages building on top of numpy/scipy/pandas, like the PyAstro stack, continue
to work with these updates, despite some new test failures.
Matthias
[1] https://wiki.debian.org/Python/Python3.8.
[2]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=python3.8;users=debian-python@lists.debian.org
Reply to: