[Distutils] RFC: Updating PEP 345

[Tres Seaver]

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

Tarek Ziadé wrote:
> Jim started a branch during Pycon, maybe you can push your work over
> there for review here ?

AFAICT, Jim hasn't checked anything into that branch:

> $ svndiff http://svn.python.org/projects/peps/{trunk,branches/jim-update-345}/pep-0345.txt
> $ svn log --stop-on-copy http://svn.python.org/projects/peps/branches/jim-update-345
> ------------------------------------------------------------------------
> r70636 | jim.fulton | 2009-03-27 15:19:28 -0400 (Fri, 27 Mar 2009) | 1 line
> 
> Update meta data reflecting work in setuptools

I am not (yet) a Python committer;  if I were so blessed, I would be
glad to commit this change on that branch.

> Also, I am wondering if we shouldn't merge it with PEP 376, where we
> might want to add a REQUIRES file
> into the egg.info structure, besides the PKG-INFO file.

I wouldn't chunk those changes:  the PEP which specifies the PKG-INFO
format needs to have a clear history.

If PKG-INFO is extended to hold distribution-level requires / provides /
obsoletes, then I can see no reason to add another generated file inside
egg-info (which already contains PKG-INFO).


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ3jD4+gerLs4ltQ4RArsXAJsHcW/cI5hRiuzOQ/zgvIF4SbGoWACeMzMV
HWBIMloJDE4OE+UQI3zxaWo=
=i/wZ
-----END PGP SIGNATURE-----