On Mon, May 21, 2012 at 4:32 PM, Benjamin Peterson
2012/5/20 Nick Coghlan
: On Mon, May 21, 2012 at 3:47 PM, Terry Reedy
wrote: On 5/21/2012 12:28 AM, Nick Coghlan wrote:
On Mon, May 21, 2012 at 11:23 AM, Guido van Rossum
wrote: I suggest that we add a separate (virtual) subdomain, e.g. docs3.python.org.
I was about to post the exact same idea.
Please, no - proliferating subdomains can quickly get confusing and hard to remember. It makes sense up to a point (e.g. separating out the docs from everything else on python.org), but having multiple docs subdomains is completely unnecessary when we already have directory based versioning.
Namespaces are a great idea, let's do more of those :)
A subdomain isn't a namespace?
A subdomain is only a namespace if you use it as one. The following would be using docs.python.org as a namespace (and is what I think we should move towards): docs.python.org/latest docs.python.org/dev docs.python.org/3.2 docs.python.org/3.1 docs.python.org/2.7 docs.python.org/2.6 etc... The following is *not* using it as a namespace: docs.python.org # 2.7 docs3.python.org # 3.2 Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia