On Tue, 20 Oct 2009 13:53:31 +0100, Chris Withers <ch...@simplistix.co.uk> wrote: > Be very aware of the problems of proliferating boilerplate code > (buildout has already suffered this): > > - old versions will have to work forever > > - bug fixes are *very* hard to do
Well, you're probably right. So I will build an option in to check on the net for an updated version before starting. > > I would like my setup.py to look like: > > from xxx import setup > setup() > > ...and have all the code be in xxx. If xxx is a separately available > package for python<2.7, then fine. > > I would prefer to see "hard logic" in setup.py where there is a good > programming language to support it any everything else in setup.cfg Of course. Code in one place, data in another. > (don't like .info, sorry ;-) ). I'm softening. > My hunch is that for 95% of packages, > setup.py will be nothing more than the above... Hope so David _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
