3 ms·
This isn't intended to be obstreperous, but I'm genuinely curious: How many Python developers are in a position to really care about 2 vs 3? The people I know
by analog31 12y ago
This isn't intended to be obstreperous, but I'm genuinely curious: How many Python developers are in a position to really care about 2 vs 3?
The people I know who use Python, including myself, range from utter beginners to experienced programmers, but are using a relatively small subset of the available libraries, and are just using whichever version we started with. I could translate my code to version 3 in a heartbeat, but have no particular reason to do so. I've translated some of my most important stuff from BASIC to Python after all.
Professional developers will do whatever is right for their projects.
My concern would be for the folks who develop and maintain the libraries -- for whose generosity I'm grateful. If there were some sort of consensus on the direction of Python, I'd hop on the bus just to make life easier for those developers. Their time would be better spent adding useful features or just combing the code for bugs, than coping with multiple Python versions.
Could a single Python interpreter somehow manage a mixture of 2 and 3 code?
- shadowmint 12y agoIf python 3 hadnt chosen to swap all its internals for unicode this miiiight have been plausible; but as it stands the bizaar 'python X' language subset that runs on both is about as good as it gets unfortunately.
- ak217 12y ago> Could a single Python interpreter somehow manage a mixture of 2 and 3 code? You could write code for a subset of 3 that would be fully functional on 2. There are a number of efforts out there to provide the missing compatibility layer that opened a chasm between Python 2 and 3. My contribution is https://github.com/kislyuk/eight https://github.com/kislyuk/eight. Depending on what you're doing, writing code that is compatible with even the easiest combination of versions (2.7 and 3.3) can be unreasonably hard, and the officially recommended migration tools suck. IMO this has to do with a few unfortunate design decisions made back in the 2.x days (most egregiously the ascii default encoding and silent Unicode coercion), combined with an unwillingness to admit that 3.0-3.2 were really bad in not providing a migration path and work on a more comprehensive migration strategy and backports library.
- msl09 12y agoMost libraries are migrating and honestly I haven't seen that much complaint in places other than ycombinator
- chris_mahan 12y agoI need pygraphviz in 3 and it's not. :( I guess I have to roll up my sleeves on that one. It's a dependency for networkx, to draw diagrams...