Firefox/Python 3 Migration: Difference between revisions

Jump to navigation Jump to search
→‎How We Get There: mention key libraries
(tweak dates, tweak porting instructions)
(→‎How We Get There: mention key libraries)
Line 11: Line 11:
Next we:
Next we:


* Build interpreter switching mechanisms into the toolchain so we can run sub-components in just 2 or just 3. (mach sub-commands, py_action)
# 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)
# Make key support libraries run in both Python 2 and Python 3. (mach-core)
* Port Python 2-only components to Python 3 piecemeal.
# Build interpreter switching mechanisms into the toolchain so we can run sub-components in just 2 or just 3. (mach sub-commands, py_action)
* Remove Python 2 compatibility. (When that might happen needs discussion. Possibly sometime in 2020.)
# Port Python 2-only components to Python 3 piecemeal.
# Remove Python 2 compatibility. (When that might happen needs discussion. Possibly sometime in 2020.)


== Getting Involved ==
== Getting Involved ==
75

edits

Navigation menu