[Distutils] RFC : PEP 376 - egg.info

P.J. Eby pje at telecommunity.com
Mon May 4 17:48:50 CEST 2009

At 07:34 PM 5/3/2009 +0200, Tarek Ziadé wrote:
>2009/5/3 P.J. Eby <pje at telecommunity.com>:
> > At 12:03 PM 5/3/2009 +0200, Tarek Ziadé wrote:
> >>
> >> The name of each file will have to be normalized: all upper case with
> >> no extensions.
> >>
> >> Any opinions ?
> >
> > I don't see any point to the normalization.
>To avoid different naming conventions like:
>PKG-INFO, requires.txt, SOURCES.txt

And the problem with that is...?

> >  However, being able to install
> > arbitrary files in .egg-info is currently supported by setuptools, and that
> > capability is used by e.g. the EggTranslations project.
> >
> > I would therefore suggest that perhaps the ability to specify 
> file trees for
> > egg-info inclusion would be better,
>Are you talking about the directory that is built by egg_info in setuptools ?
>or something else ?
>I mean, do we want to have subdirectories in .egg-info ?

They already exist.

> >  if the goal is to eventually replace
> > setuptools.
>The goal is to provide an install_egg_info command that can be configured
>without the need to replace/override it.
>I guess, this can be done by taking part of the code done in setuptools
>install_egg_info and provide a way for setuptools or another project
>to add more files
>through configuration.

setuptools simply copies a pre-built egg-info directory from the 
source tree, that is built by the "egg_info" command.  But people can 
also put arbitrary files and directories there, besides the contents 
built by the command itself.

>Maybe this straight-forward sentence would work better:
>"let's add entry points in Distutils" ?


More information about the Distutils-SIG mailing list