Hi Sandro, Upstream README seems to indicate that there is no release that supports *both* python 2.7 and 3.7 so this is not a choice between 2.0 and 1.9.
More likely, two source packages are required for buster. Alternatively one of Python 2 / Python 3 must be dropped from pylint (presumably Python 2). If these are the options, which are you intending to follow? 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 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? For me, at least, the inability to have pylint3 installed and test out python3.7 on the same machine is now hindering other Debian work, including the work that I wanted to do this week at DebCamp. cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
