On Wed, Sep 19, 2018 at 09:32:23AM -0400, 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) I think for “popular” packages duplication is unavoidable. Sphinx 2.0 will also drop Python 2.7 support, so I am going to make the “sphinx” source package ship only python3-sphinx, and introduce the new source package (“sphinx-python2”?) which will ship only python-sphinx. Eventually I will also do a mass bug filing, but with the current 314 python-sphinx reverse build-depends it is clear that I will have to ship sphinx-python2 for quite some time. -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature