> Upstream README seems to indicate that there is no release that supports > *both* python 2.7 and 3.7
i know, that's exactly my point > so this is not a choice between 2.0 and 1.9. well it is: it can be decided to ignore the 2.x branch and stick with 1.9 for buster (which support python 2 and python 3 up to 3.6) and not build astroid/pylint for 3.7 which possibly wont be the default py3k in buster (but it's hard to tell as common developers dont get much insight in the decisional process) > More likely, two source packages are required for buster. Alternatively one of i'm not really a fan of keeping 2 packages sets around > Python 2 / Python 3 must be dropped from pylint (presumably Python 2). If > these are the options, which are you intending to follow? i dont know, that's what's holding up a resolution for this bug! on one hand we still want to support python 2 in buster, so that's a compelling reason to keep python 2 support in pylint, OTOH we want to introduce 3.7 as (at least) a supported version, and the only way to make pylint available for 3.7 is to drop entirely support for python2. few other project i maintain are planning on released a py3k-only version, so maybe that's the direction to go with such modules? > On Sunday, 22 July 2018 15:52:04 AEST Sandro Tosi wrote: > > thanks for ignoring the next paragraph in that email, so let me re-add it > > here: > > > > ``` > > since astroid/pylint only support python 3.4+, it is not as simple as > > package the new version and upload it; i'm not even (yet) sure buster > > should have 2.0 but maybe it should to 1.9 > > ``` > > No-one is ignoring that statement, just hoping that there is progress towards > a solution rather than statements of what the problem is. We have all read the until your email, there werent any solutions proposed by external parties, so thanks for that, i think we should still understand how to approach it in the right way. > bug log and know the problem. You've indicated that you don't want help, but > not what the timeline to a fix is. If time is a problem to deal with RC bugs, > perhaps you'd be happy for team mates in PAPT to deal with this? that's correct: i dont need help to prepare a trivial patch to update astroid/pylint to the latest version, that's something anyone can do; what i'm concerned here is what approach to follow for packages dropping support for python releases Debian still cares to support. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
