[Raymond] >> There should probably be a PEP sets clearer guidelines about what should be backported from Py3.0. >> >> Perhaps something like this: >> * If there is a new feature that can be implemented in both and will make both more attractive, then it should be in both. >> * If something is going away or changing in 3.0, then the 2.6 conversion tool mode should warn about it if possible. >> * If neither of the above apply, then leave 2.6 alone. [Guido van Rossum] > Can you volunteer a draft? It could be PEP 3003. I'm probably too > close to 3.0 to be able to objectively write this, which really > represents end users' desire for stability in 2.6. Yes. Will do. Raymond
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