there are currently 2 source packages:

astroid: on the 1.x branch, builds python-astroid and python3-astroid
pylint: on the 1.x branch, builds pylint (depends on python-astroid),
pylint3 (depends on python3-astroid), pylint-doc

the only way forward to keep compat with python2 while supporting 3.7 i see is:

astroid: uses the 2.x branch, builds only python3-astroid
pylint: uses the 2.x branch, builds only pylint3, pylint-doc
NEW astroid2: remains on the 1.x branch, builds only python-astroid
NEW pylint2: remains on the 1.x branch, builds only pylint (depending
on python-astroid)

astroid2 and pylint2 will be dropped after buster is released, keeping
only astroid and pylint in bullseye

adding ftpmasters in the loop as a headsup since this plan would
require a bit of coordination to reduce users disruption during the
migration of the bin pkgs from one src pkg to the new ones.

what people feel about it? just to make it clear: i'm not really
excited about the package duplication, although it's the only viable
solution i can see for now. comments/suggestions welcome

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Reply via email to