On Fri Aug 08 2014 at 2:59:04 PM Claudiu Popa <pcmantic...@gmail.com> wrote:
> On Fri, Aug 8, 2014 at 9:09 PM, Brett Cannon <bcan...@gmail.com> wrote: > > > > I just realized I should have checked setup.py to see if 2to3 was being > > used, which it is. =) So it seems that I will have to port Pylint over > to a > > Python 2/3 source-compatible code base in order to pass any checks with > my > > set of checkers against Pylint itself. Is that okay? And if so what > Python > > version support is required (Tox file suggests 2.7, 3.2-3.4)? > > > > > Right now, Pylint 1.3 is the last version which supports 2.5 and 2.6 > and starting with Pylint 1.4, which will be released really soon, it > will support only 2.7-3.4. So having a Python 2/3 source-compatible > base is the way to go for the near future. I believe we'll drop 2to3 > as well. A pull request for this will be appreciated. :-) > Any issue if I just make it part of my Python 3 checker pull request? It's obviously easier when I have my own checkers to make sure I'm not screwing it up. =)
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
