Size: 1405
Comment:
|
Size: 1541
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 8: | Line 8: |
* This will require converting 3 Python 2-compatible packages to a common subset of Python 2 and Python 3. We may or may not be able to do this using 2to3; 2to3 may be a bit too exuberant about moving to a nice, python 3-only syntax in some areas. 1. logilab common |
* This will require converting 3 Python 2-compatible packages to a common subset of Python 2 and Python 3. We may or may not be able to do this using 2to3; 2to3 may or may not prove too exuberant about moving to a nice, python 3-only syntax in some areas. 1. logilab-common |
Line 13: | Line 13: |
1. logilab astng | 1. logilab-astng |
Line 15: | Line 15: |
* There appear to be test suites for each of these, which can be invoked using the pytest command, which in turn appears to be part of logilab-common itself * The owners of the code would like to keep the changes compatible with Python 2.5.x, which of course is a bit more involved than targeting 2.6 and up. |
* There appear to be test suites for each of these, which can be invoked using the pytest command - pytest appears to be part of logilab-common, which suggests a bit of mutual dependency to work around. * The owners of the code would like to keep the changes compatible with Python 2.5.x to avoid having two code bases to maintain, which of course is a bit more involved than targeting 2.6 and up. |
Line 20: | Line 22: |
* Python Wiki on [[2to3]] |
This page describes efforts to port pylint to Python 3.x
Status of the port
We're really just getting started.
Goals and high level overview of tasks
The idea is to eliminate Python 2.4 compatibility because that will simplify some of the code, and to expand compatibility to 3.0 and 3.1.
- This will require converting 3 Python 2-compatible packages to a common subset of Python 2 and Python 3. We may or may not be able to do this using 2to3; 2to3 may or
- may not prove too exuberant about moving to a nice, python 3-only syntax in some areas.
- logilab-common
- This one is probably the place to start, because it appears to contain the test harness we need, and the owners of the code believe it will
- be the easiest part
- This one is probably the place to start, because it appears to contain the test harness we need, and the owners of the code believe it will
- logilab-astng
- pylint itself
- There appear to be test suites for each of these, which can be invoked using the pytest command - pytest appears to be part of logilab-common, which suggests a bit of
- mutual dependency to work around.
- The owners of the code would like to keep the changes compatible with Python 2.5.x to avoid having two code bases to maintain, which of course is a bit more involved
- than targeting 2.6 and up.