4 ms·
What modules? Your idea is probably the wrong way to approach the problem. You could look at execnet if you just need to run hopelessly old unmaintained stuff t
by pekk 13y ago
What modules? Your idea is probably the wrong way to approach the problem. You could look at execnet if you just need to run hopelessly old unmaintained stuff that you can't push to get ported.
- davvid 13y agoThere 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.
- ginko 13y agoGoogle Protocol Buffers. I want to use those for exporting scene information from Blender. Blender uses Python 3 for scripting and the protobuf code generator and libraries only support Python 2.x. The same for Apache Thrift. Both are very well maintained, they are just not planning to move to Py3 any time soon.