[Python-Dev] Distutils2 scripts
ziade.tarek at gmail.com
Fri Oct 8 15:38:47 CEST 2010
2010/10/8 Michael Foord <fuzzyman at voidspace.org.uk>:
> On 08/10/2010 14:28, Dirkjan Ochtman wrote:
>> On Fri, Oct 8, 2010 at 15:22, Tarek Ziadé<ziade.tarek at gmail.com> wrote:
>>> Mmm.. setup.py is gone in D2, and setup.py will be the marker of d1.
>> So, sorry for backing up to this, but isn't it true that many projects
>> do custom stuff in their setup.py that they wouldn't be able to do in
>> setup.cfg? Is the goal really to make that impossible/unnecessary?
> The goal is to make it unnecessary. My understanding is that it will still
> be possible to use a setup.py, just unnecessary for the vast majority of
Yes. And to make it possible to keep a d1 setup.py, which works with
all installers out there, we decided that d2 would ignore that file,
and provide other ways to hook code if necessary.
IOW one project may provide a d1 setup.py and a d2 configuration in
the same release.
> All the best,
>> Mercurial, for example, we have a fairly large setup.py that helps us
>> deal with many kinds of issues: incomplete Python installations on
>> different platforms, adding packages depending on the platform, do
>> custom stuff to compile gettext files, etc...
>> Python-Dev mailing list
>> Python-Dev at python.org
> READ CAREFULLY. By accepting and reading this email you agree,
> on behalf of your employer, to release me from all obligations
> and waivers arising from any and all NON-NEGOTIATED agreements,
> licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
> confidentiality, non-disclosure, non-compete and acceptable use
> policies (”BOGUS AGREEMENTS”) that I have entered into with your
> employer, its partners, licensors, agents and assigns, in
> perpetuity, without prejudice to my ongoing rights and privileges.
> You further represent that you have the authority to release me
> from any BOGUS AGREEMENTS on behalf of your employer.
Tarek Ziadé | http://ziade.org
More information about the Python-Dev