I am -1 on renaming anything unless it solves a technical problem. Forever after we will have to explain "well, it used to be called X, now it's called Y..."
On Tue, Mar 26, 2013 at 5:01 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Tue, Mar 26, 2013 at 4:08 PM, PJ Eby <p...@telecommunity.com> wrote: >> On Tue, Mar 26, 2013 at 3:03 PM, Daniel Holth <dho...@gmail.com> wrote: >>> I think PKG-INFO is a highly human-editable format. >> >> That doesn't mean you necessarily want to edit it yourself; notably, >> there will likely be some redundancy between the description in the >> file and other files like the README. >> >> Also, today one of the key use cases people have for custom code in >> setup.py is to pull the package version from a __version__ attribute >> in a module. (Which is evil, of course, but people do it anyway.) >> >> But it might be worth adding a setuptools feature to pull metadata >> from PKG-INFO (or DIST-INFO) instead of generating a new one, to see >> what people think of using PKG-INFO first, other files second. In >> principle, one could reduce a setup.py to just "from setuptools import >> setup_distinfo; setup_distinfo()" or some such. > > In other words, using d2to1 and only for `setup.py egg_info` (only not > egg_info but whatever we're doing instead to generate the metadata ;) > > Erik _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
