On 09/19/2018 03:32 PM, Sandro Tosi wrote: >> This also means finding >> solutions for edge-cases such as astroid, whose 2.0 branch is the only to >> support Py3.7, but also drops 2.x support. > > this is becoming less of an edge-case and more the current situation > of several "core" python modules: drop python2 support (eventually > maintaining a LTS-like old release around for py2) in favor of a pure > python3 codebase. Latest example is matplotlib 3.0 released yday which > dropped python2 support (maintained only in the 2.x branch, which will > receive only critical fixes), and numpy will release soon a py3k-only > version. > > What did the team decide on this front? duplicating packages is not > always feasible (both from an archive and from a maintainership > perspective)
Unless you've found hundreds of cases, it's very much ok to do package duplication for these few cases where we need 2 different source packages, and only for the next following months that we have before the freeze. How many cases are we talking about? Not even a full dozen? If you can't handle the workload, it's also ok to ask for help, but that doesn't seem to be your way. I'm kind of disappointed to see no answer to #902631 from you in this regard, leaving the bug open for nearly 3 months now. Could you at least let Nicolas do the upload? Cheers, Thomas Goirand (zigo)
