[Distutils] RFC: Updating PEP 345

[Tarek Ziadé]

On Thu, Apr 9, 2009 at 7:31 PM, Tres Seaver <tseaver at palladion.com> wrote:
> -----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.

ok, maybe you can push it to the wiki then, and I'll commit it when it's ready ?

>
>> 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).

Because setuptools does it. It adds a requires.txt file separated from PKG-INFO.
But it would make sense not to have a second file.

Tarek