[Distutils] setup.cfg new format proposal
ziade.tarek at gmail.com
Sun Sep 13 00:31:33 CEST 2009
On Sat, Sep 12, 2009 at 4:42 PM, Floris Bruynooghe
<floris.bruynooghe at gmail.com> wrote:
> On Sat, Sep 12, 2009 at 02:52:17AM +0200, Tarek Ziadé wrote:
>> On Fri, Sep 11, 2009 at 5:49 PM, Tarek Ziadé <ziade.tarek at gmail.com> wrote:
>> >> I agree that more background and motivational information would be
>> >> very helpful, as would some real world examples. I know that >90%
>> >> (maybe 99% :) of the packages I distribute don't adapt to their
>> >> execution context (beyond what distutils does internally) or need
>> >> anything but meta data.
>> That's a first draft:
> Your example shows an empty setup() call but does not say which
> package/module is supposed to be installed.
I'll complete it, right.
> I'm confused now to how much you would like in setup.cfg. Is the idea
> to leave the package/module/extension module/scripts etc in setup.py?
The target is to push all fields that belong to the Metadata (see PEP 314)
in the static file.
So anything else required by a command would stay in setup.py
More information about the Distutils-SIG