Aaron Meurer asmeurer at gmail.com
Fri Jul 25 23:13:27 CEST 2014

• Previous message: [Python-porting] Pylint checkers for Python 2/3 compatibility
• Next message: [Python-porting] Pylint checkers for Python 2/3 compatibility
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

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

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
>

---

• Previous message: [Python-porting] Pylint checkers for Python 2/3 compatibility
• Next message: [Python-porting] Pylint checkers for Python 2/3 compatibility
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-porting mailing list