> Even in the plans that involve 2to3 > though, "drop everything prior to 2.6" was always supposed to be step 0, > so "single codebase" adds much less of a burden than I thought. Are you talking about general porting, or about Twisted? It is a common misconception that "drop everything prior to 2.6" was a recommended step 0 for porting to Python 3. That was never recommended. Instead, what *was* recommended is "port to Python 2.6", which for many projects already supporting, say, 2.5, was a no-op, so people read more into that than was actually necessary. With the project ported to 2.6, you could then make use of the 3k warnings to learn what issues you would face when porting to 3k. 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