On Tue, 27 Oct 2009 16:52:36 +0000, Chris Withers <ch...@simplistix.co.uk>
wrote:
> from distutils.core import setup,parse_static
> setup(**parse_static('setup.cfg').to_dict())
>
> ...and of course, because setup.cfg is the default name, we just end up
> with:
>
> from distutils.core import setup
> setup()
Nice..
But one still ends up with a user based setup.py
After OPs comments about security I'm totally convinced that we need
to ban setup.py, or at a very minimum move a standard setup.py into
distutils itself.
So one would say..
setup.py --install mypackage.egg
or
setup.py --install mypackage.tgz
(from any directory)
In simple cases, setup.py programs don't add any value.
All the information required to do a package install is
pretty much all to be found in the PKG_INFO file anyway.
For typical packages, that is.
So we could even wave the magic wand on:
> from distutils.core import setup
> setup()
making it just '' (disappear) if we wanted..
We'd just have to add a script to distutils. I'm not
sure how hard that is.
David
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
