Home Original page

[Python-porting] Pylint checkers for Python 2/3 compatibility

Brett Cannon bcannon at gmail.com
Sat Jul 26 16:59:39 CEST 2014 
On Fri Jul 25 2014 at 5:13:47 PM Aaron Meurer <asmeurer at gmail.com> wrote:

> How smart are the checkers, relative to, say, the sorts of things that
> 2to3 looks for (or modernize or futurize)?
>

They are smarter as the checkers have more information (e.g. is this a
method and not a function, is this a built-in and not just something named
'map').

-Brett


>
> Aaron Meurer
>
> On Fri, Jul 25, 2014 at 1:42 PM, Brett Cannon <bcannon at gmail.com> wrote:
> > I think I've reached beta quality for caniusepython3 3.0.0 where I have
> > implemented custom Pylint checkers for various things that will break in
> > Python 3 (e.g. referencing built-ins that are removed or have different
> > semantics, etc.). The goal with the checkers is for projects to use them
> > after running modernize(3k) or futurize on their code to prevent
> regressing
> > their Python 2/3 source-compatibility.
> >
> > The code can be found at
> > https://github.com/brettcannon/caniusepython3/tree/pylint . Feedback is
> > welcome before I make an official release.
> >
> > _______________________________________________
> > Python-porting mailing list
> > Python-porting at python.org
> > https://mail.python.org/mailman/listinfo/python-porting
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20140726/bf09174d/attachment-0001.html>
More information about the Python-porting mailing list