On Fri, Oct 8, 2010 at 15:22, Tarek Ziadé <ziade.ta...@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? In
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...

Cheers,

Dirkjan
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to