> 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) -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
