75
edits
(tweak dates, tweak porting instructions) |
|||
| Line 14: | Line 14: | ||
* Make Python 3 porting and development safe by adding a Python 3 option to the developer toolchain. (mach lint, parts of the test suite) | * Make Python 3 porting and development safe by adding a Python 3 option to the developer toolchain. (mach lint, parts of the test suite) | ||
* Port Python 2-only components to Python 3 piecemeal. | * Port Python 2-only components to Python 3 piecemeal. | ||
* Remove Python 2 compatibility. (When that might happen needs discussion | * Remove Python 2 compatibility. (When that might happen needs discussion. Possibly sometime in 2020.) | ||
== Getting Involved == | == Getting Involved == | ||
| Line 30: | Line 30: | ||
** If using `tox`, then adding `py35`, and `py36` to the list of environments should be sufficient | ** If using `tox`, then adding `py35`, and `py36` to the list of environments should be sufficient | ||
** If using |mach python-test|, make sure the relevant manifest doesn't skip-if Python 3 and run |mach python-test --python 3 <path>|. | ** If using |mach python-test|, make sure the relevant manifest doesn't skip-if Python 3 and run |mach python-test --python 3 <path>|. | ||
* [http://python-future.org/futurize.html#stage-1-safe-fixes `futurize`] | * [http://python-future.org/futurize.html#stage-1-safe-fixes `futurize` Stage 1 fixes] can be used to transform code into code that's compatible with both python2.7 and python3 | ||
* The `six` module is available in-tree, feel free to use it as a dependency | * The `six` module is available in-tree, feel free to use it as a dependency | ||
edits