[Catalog-sig] PEP 314: latest draft
Wed, 30 Apr 2003 08:07:37 +1000
Content-Description: signed data
On Wednesday 30 April 2003 03:36 am, Andrew Kuchling wrote:
> An open issue: with the addition of Classifiers, should the
> Platforms and License fields be deprecated and/or removed?
> (My vote is to remove Platforms and License, ignoring them when
> they're supplied to distutils.core.setup(), and warning the user when
> they run "sdist" and those keywords are supplied.)
I've had instances where users have included the entirety of their license =
the license field. The question is whether that's appropriate. I also vote=
for removing Platforms and License.
It also seems strange that the PKG-INFO format it described even though tha=
not the human-editable version. It would seem to be a good idea to at least=
describe the format of the input data (ie. setup.cfg and setup.py).
> The PKG-INFO file format is a single set of RFC-822 headers
> parseable by the rfc822.py module. The field names listed in the
> following section are used as the header names. There's no
> extension mechanism in this simple format; the Catalog and Distutils
> SIGs will aim at getting a more flexible format ready for Python 2.2.
> Description (optional)
> A longer description of the package that can run to several
> paragraphs. (Software that deals with metadata should not
> assume any maximum size for this field, though one hopes that
> people won't include their instruction manual as the
I believe we should ask for adherence to the ReST format here. Simple=20
paragraphs for most descriptions and use of ReST formatting if you want to=
get fancy. At the moment I'm <pre> formatting the description in PyPI becau=
I don't know whether I can trust the input data.
> Home-page (optional)
> A string containing the URL for the package's home page.
> Home-page: http://www.example.com/~cschultz/bvote/
> Author (optional)
> A string containing at a minimum the author's name. Contact
> information can also be added, separating each line with
> Author: C. Schultz
> Universal Features Syndicate
> Los Angeles, CA
PyPI will have to be modified to handle this spec :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----