Jim Fulton wrote: > > isn't >> the same as coding the configuration file in the script. That might >> be okay too, but config+script isn't the same as a script, it's >> something else. > > OK, we disagree. People encode this sort of information in scripts > now, Saying it is something else doesn't make it so. If no one else > is interested in this, we'll try to figure something out and share what > we've learned.
Maybe I should clarify what I mean. The script that setuptools generates, as enumerated in the setup.py file, isn't something that would naturally be bound to any configuration file. There's not a one-to-one mapping between those scripts, an installation, and a single configuration file. That *a* script might be bound to a configuration file, sure. Such a binding might also include any number of environment setups; the typical items in a shell script. Unless you are thinking about a different kind of configuration than I am. I suppose configuration like an enumeration of activated plugins would seem to fit more closely with a working environment. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
