On October 26, 2019 8:09:47 PM UTC, "Rebecca N. Palmer"
<rebecca_pal...@zoho.com> wrote:
>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
I certainly can't provide an authoritative answer to the question, but if it
were me, unless there are important rdepends that might cause pandas to be kept
if we end up not being able to completely ditch python2, I would drop the
python-* package(s) and move on. Transient support for things soon to be
removed/updated isn't worth the trouble.
I haven't checked the rdepends, so I don't have any opinion about which case
applies in this instance.
Scott K
