-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tarek Ziadé wrote:

On Tue, Nov 17, 2009 at 10:28 PM, Tres Seaver wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Tarek Ziadé wrote:

...

That's why I said that 100% of the information could stay in PKG-INFO (==the metadata), instead of having to maintain something else at PyPI. Apoligies for misunderstanding: I thought you were arguing to remove the field from PKG-INFO. I'm fine with removing any mandate for a registry from the PEP.

That's fine, probably related to my frenglish too.

There's one thing though: do we want the url and description data with the name ?

I would say we don't need anything. This field is like the "data type" stuff (not yet in a PEP): we want the downstream folks from Fedora / Debian to suggest values to the upstream (PyPI) package maintainer. I think we can get "enough" traction from just having a well-understood name ('zlib', 'libxslt', etc.) in this field. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAksDHUkACgkQ+gerLs4ltQ5PbQCeOV980LniLELp1PROe8Vyyh1u bEkAoMv135Mhk/V4w8u1Og++JJNbUr56 =v5Kr -----END PGP SIGNATURE-----