MRAB wrote: > Terry Reedy wrote: >> Dirkjan Ochtman wrote: >> >>> It needs to be decided where the hg repositories will live. I'd like >>> to propose to keep the hgwebdir instance at hg.python.org. This is an >>> accepted standard for many organizations, and an easy parallel to >>> svn.python.org. The 2.7 (trunk) repo might live at >>> http://hg.python.org/main/, for example, with py3k at >>> http://hg.python.org/py3k/. >> >> I would very much like the 'k' dropped from the py3 name. It was a >> funny joke when py3 was vaporware, now it is excess baggage which only >> puzzles non-insiders and newcomers. >> >> I think the two repos should be either symmetrically named >> >> hg.python.org/py2 >> hg.python.org/py3 >> >> If one must be designated 'main', it should be py3. >> >> Continuing to call py2 'main' will continue to discourage use of py3. >> > We could regard py3k as the phase from the original concept of Python 3 > to its 'prototype', Python 3.0. Right. And that phase is over, especially with Barry posting today on python-list that there will be no more 3.0.x releases ever. > Python 3.1 would be the first 'real/usable' version. Right. 'is'. as Barry also posted. tjr
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