>>>> You seem to be implying that some projects may release separate >> >> source distributions. I cannot imagine why somebody would want to >> >> do that. >> > >> > That's odd. I can't imagine why anybody would *not* want to do that. >> > Given the number of issues 2to3 can't fix (because it would be too >> > dangerous to guess) >> >> Like which one specifically? > > Anything having to do with the str->bytes/unicode->str move is so far > off-limits to 2to3. Sure - but does that mean you need to separate code bases? Why does this move prevent people from running the same code in 2.x and 3.x? In 2.x, they should use Unicode objects for text and regular strings for binary data, and such code will run fine after converted by 2to3. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4