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

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

Bug#942106: (some kind of) transition: add python3.8 as a supported python3 version

Cross-posted to 3 groups.

Show key headers only | View raw

What should be done with modules where Python 3.8 compatibility requires 
moving to a new upstream release that doesn't support Python 2, but the 
Python 2 package still has dependencies (so can't be removed yet under 
existing rules)?

- Split them into two source packages with different upstream versions, 
as was done for matplotlib and numpy?
- Remove the Python 2 package anyway?
- Let them be broken in Python 3.8 for now?

e.g. pandas dropped python2 support in 0.25.0, and gained python3.8 
support in 0.25.2:
https://github.com/pandas-dev/pandas/issues/29043

Ubuntu got pandas 0.23 to build with python3.8, but only by ignoring 268 
test failures (I haven't yet had time to assess their severity):
https://bugs.launchpad.net/ubuntu/+source/pandas/+bug/1849374
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/p/pandas/20191024_181815_7c017@/log.gz

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

Thread

Bug#942106: (some kind of) transition: add python3.8 as a supported python3 version "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2019-10-26 22:30 +0200
  Bug#942106: (some kind of) transition: add python3.8 as a supported python3 version Matthias Klose <doko@debian.org> - 2019-10-27 00:00 +0200
    Bug#942106: (some kind of) transition: add python3.8 as a supported python3 version "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2019-10-27 00:40 +0200
      Bug#942106: (some kind of) transition: add python3.8 as a supported python3 version "Rebecca N. Palmer" <rebecca_palmer@zoho.com> - 2019-10-27 12:30 +0100

csiph-web