David Lyon wrote:
Why is it that you basically want to put an entire module's worth of
code inside every single package's setup.py?
Because it is easy.
Let me put it another way - how does a 'normal-user' update distutils
in the stdlib?
easy_install/pip/etc distutils
...with the new version on PyPI.
If that's not preferred, then they'd wait for Python 2.7, and do:
from distutils.core import setup
setup()
Well, 500 lines is just this week. Maybe by next week it will be even more.
If the file is 100kb long, I don't think a user would care.
I'm "a user" in this case, and I care... The maintenance burden a file
like the setup.py you're proposing places on me as a package author in
making sure the packages I maintain all include the right setup.py, and
needing to bump my package's versions when code that has nothing to do
with my package has bugs fixed isn't acceptable.
I don't think users in the real world will look at the file..
What happens for the author of one of the small number of packages that
actually needs to have logic in setup.py?
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
