Fred Drake wrote:
For the many packages that don't need that level of flexibility, using
a tool that consumes static metadata is a major win, so long as we
keep in mind that tools need to be able to determine when that static
metadata is sufficient. That allows the development of tools that can
usefully get things done *and* refuse to run untrusted code
themselves.
I like the idea (I think I saw it in 390 or one of the other PEPs in
this aread) that:
setup()
...would get everyone from the static metadata file, while any keyword
parameters to setup would override the appropriate setting from the
static metadata file...
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
