Hi Claudiu, I submitted PR https://github.com/PyCQA/astroid/pull/516.
Unfortunately it fails some pylint checks on py35, but failures seem to be on files not related with the PR itself: I'm leaving the PR untouched. francesco On 16 March 2018 at 13:51, Claudiu Popa <pcmantic...@gmail.com> wrote: > Hi Francesco, > > Yes, definitely, sounds like a good idea! For astroid and pylint's > maintenance > branches we prefer PRs on top of the corresponding branches rather > than on top of the tag. > There's currently no release schedule planned for 1.6.2, we just have to > release > it on PyPi. SInce we already have a couple of more PRs that were > backported, > I'm going to do it today. > > Thanks! > Claudiu > > On 16 March 2018 at 12:27, Francesco Tartaggia > <francesco.tartag...@etiqa.it> wrote: > > Hi all, > > > > I'm writing about PR https://github.com/PyCQA/astroid/pull/478 (Fix > > submodule import in six.moves). > > > > Are you interested in backporting the fix from master branch to the 1.6 > > release branch? > > > > Doing so would fix the "Unable to import 'six.moves.urllib.parse' > > (import-error)" issue for pylint, without modifying pylint's astroid > > dependency declaration. > > > > If so, do you prefer a PR right on top of latest released tag > > "astroid-1.6.1" or on top of branch 1.6? > > What are the release schedule for astroid-1.6.2? > > > > Best regards, > > francesco tartaggia > > > > > > _______________________________________________ > > code-quality mailing list > > code-quality@python.org > > https://mail.python.org/mailman/listinfo/code-quality > > >
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
