Ian Bicking schrieb:
On second thought, simply by using a read-only domain (one that has no
admin on the domain itself) you'd also be fine. So
http://pypidocs.python.org/package/* would work fine, so long as all the
management for that remained on pypi.python.org.
I personally like domains for projects, though package.pypi.python.org
is a bit long winded anyway. A new top-level domain (pypackage.org or
pyforge.org or something) would mitigate that. But any place to drop
docs would be nice. Especially with Sphinx I think we'll get more
libraries with multi-page HTML docs.
JFTR, I also like the look of http://package.pypi.python.org/ and would
vote for subdomains if it can be done with decent normalization.
Of course, we can also only offer the domain to those distributions
with suitable names.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.
_______________________________________________
Catalog-SIG mailing list
[email protected]
http://mail.python.org/mailman/listinfo/catalog-sig
