[Imported from Trac: page Python3, version 16]

itamarst 2020-09-11 18:11:53 +00:00
parent d614b4cdac
commit 916e73c59a

@ -92,7 +92,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 on way to approach this: Here's on way to approach this:
1. Port _only_ the test module. This involves many 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. 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.
2. Then, port the corresponding module. 2. Then, port the corresponding module.
## Other notes ## Other notes