Le jeudi 02 août 2018 à 12:39:18-0400, Sandro Tosi a écrit : > 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
That seems, for me, the best solution, provided it's temporary (which we all agree on). I had a look on porting the changes to 1.x from 2.x that would allow python3-astroid to work properly, and it seems quite a lot of work with a mixed outcome. If you wish, I'm eager to contribute into implementing this solution, but keep in mind that, as a DM, I'll eventually require your help to upload these packages. If you prefer to handle this on your own, it's fine with me, too. Thanks for considering, and cheers! -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them.
signature.asc
Description: PGP signature
