On Fri Aug 08 2014 at 2:01:18 PM Brett Cannon <bcan...@gmail.com> wrote:
> I've started work on a pull request to add my Python 3 checkers into > Pylint: https://bitbucket.org/brettsky/pylint . The work isn't quite > done, but I have run into one issue where one of my checker is causing > various regression tests to fail across the board due to strings not being > specified as either unicode or bytes. Is there an easy way to make a > checker opt-in instead of opt-out by default? Or should I go through and > fix all the strings in Pylint (probably through `from __future__ import > unicode`)? > 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)? > > On Sat Jul 26 2014 at 10:58:57 AM Brett Cannon <bcan...@gmail.com> wrote: > >> Sure. I will try to make time next week to make a pull request against >> Pylint with a checkers/python3.py or something. >> >> On Fri Jul 25 2014 at 6:14:21 PM Claudiu Popa <pcmantic...@gmail.com> >> wrote: >> >>> Hello Brett. >>> >>> At a quick glance, the patch looks really good, even with the scarce >>> documentation that we have. :-) >>> Maybe you can turn this into a pull request for Pylint, so that we may >>> have in the near future a mode that only checks Python 2/3 >>> compatibility? That way would be easier for review, too. >>> >>> Thank you. >>> >>
_______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
