PEP 301 implementation checked in

[A.M. Kuchling]

I've just checked in Richard Jones's patches implementing PEP 301, so
those of you who follow the Python CVS trunk can now play with the
code. Changes:

* The DistributionMetadata object and the setup()
function now support 'classifiers' as a keyword.
* The 'register' distutil command has been added to upload
a package's metadata to the PyPI server.

The registry is still running on my web server at amk.ca, a
bandwidth-limited DSL line, but it'll be moved to something at
python.org before too long. (Certainly before 2.3final ships!)

Please bang on the distutils code in any way you can think of, filing
bug reports and offering comments, so we can be sure that it's solid.
You can comment on the web site, too, but the site can be updated
independently of the Python code so there's less pressure to get it
finished before 2.3final.

Here's an example of how the new code works. A setup.py file can now
contain a 'classifiers' argument listing Trove-style classifiers:

setup (name = "Quixote",
version = "0.5.1",
description = "A highly Pythonic Web application framework",
...
classifiers= ['Topic :: Internet :: WWW/HTTP :: Dynamic Content',
'Environment :: No Input/Output (Daemon)',
'Intended Audience :: Developers'],
...
)

I can then run 'python setup.py register' to upload an entry to the
package index, which is currently browseable at
http://www.amk.ca/cgi-bin/pypi.cgi . ('register --list-classifiers'
will output a list of legal classifiers.)

See PEP 301 for more details. Comments are most appropriate on the
Catalog-SIG, but they'll be seen if you post them here, too.

--amk (www.amk.ca)
OLIVIA: Why, this is very midsummer madness.
-- _Twelfth Night_, III, iv