Martin v. Löwis wrote: > That doesn't mean we have to have a transition plan *now*. Creating one > after Python 3.5 is released (i.e. in 2015 or so) might be sufficient. > > To create a transition plan, you first need *consensus* that you > actually do want to transition. I don't think such consensus is > available, and might not be available for a few more years. Pushing > the issue probably delays obtaining consensus. Agreed, but that doesn't rule out discussions of what can be done to make such a transition easier. And just as 2to3 makes the overall Python transition practical, a percent to brace format translator should make an eventual formatting transition feasible. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia ---------------------------------------------------------------
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