3 ms·
There are mountains of Python 2.x code (particularly inside companies) that are well-maintained and have no plans to port to Python 3 at the moment. My approac
by davvid 13y ago
There are mountains of Python 2.x code (particularly inside companies) that are well-maintained and have no plans to port to Python 3 at the moment. My approach has generally been to make the code compatible across 2 and 3, though it requires great vigilance.
- zeckalpha 13y agoYeah this is the approach I try to take, too. Is there a good write up on the intersection of 2 and 3? I mean more than "Here's some things to look out for when you are writing for both." I mean more along the lines of the Python standard documentation, but excluding all of the incompatibilities.
- sp332 13y agoThis is sort of the opposite of what you asked for: it's the list of all "fixers" that the 2to3 program will attempt to automatically fix when converting from 2 to 3. http://docs.python.org/2/library/2to3.html#to3-fixers http://docs.python.org/2/library/2to3.html#to3-fixers If you avoid any issues not on the list, you'll have a higher chance of 2to3 being successful.