[Imported from Trac: page Python3, version 26]

chadwhitacre 2020-10-06 10:25:51 +00:00
parent 1ebf9a50d7
commit 5a782f4be4

@ -102,7 +102,7 @@ Leaking Future objects (newints, new dicts, new bytes) in module API can break e
As the port progresses, the simple "port module + its test module" gets difficult, since everything ends up depending on everything else. As the port progresses, the simple "port module + its test module" gets difficult, since everything ends up depending on everything else.
Here's one way to approach this: Here's one way to approach this:
1. Port _only_ the test module. This involves many Python 3fixes to lots of other modules, but they are not officially ported, they're just inched along just enough to make the tests pass. Since the test module is officially ported, regressions to the Python 3 port still are prevented. 1. Port *only* the test module. This involves many Python 3 fixes to lots of other modules, but they are not officially ported, they're just inched along just enough to make the tests pass. Since the test module is officially ported, regressions to the Python 3 port still are prevented.
2. Then, port the corresponding module. 2. Then, port the corresponding module.
## Other notes ## Other notes