2009/5/3 P.J. Eby <p...@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 > 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 ? > 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. Now, if entry_points were added in Distutils, things would be more simple to extend every command I guess. (like you have pointed) That's some other work we started here : http://wiki.python.org/moin/Distutils/PluginSystem But my mail to python-ideas about adding a plugin system into Python didn't get a lot of interest. Maybe this straight-forward sentence would work better: "let's add entry points in Distutils" ? Tarek -- Tarek Ziadé | http://ziade.org _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig