On Fri, Oct 8, 2010 at 3:28 PM, Dirkjan Ochtman <dirk...@ochtman.nl> wrote: > 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?
They will still be able to do it by using hooks. > 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... No the goal is to stop having setup.py as the standard for getting metadata from a project. There will always be ways to call some code in the various steps. setup.py is currently called for everything : building, installing, providing metadata etc. We want to break that and make it possible for people to express their metadata into a static file, and offer ways to express them differently depending on the platforms. See PEP 345. So you should have what you need. Now, we are still in early stages in providing these features, and I'd be happy to work on the Mercurial setup.py conversion, if it's a complex use case. So we can see how things go. Tarek > > Cheers, > > Dirkjan > -- Tarek Ziadé | http://ziade.org _______________________________________________ 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
