On 24/03/2011 4:34 AM, Ethan Furman wrote:
Michael Foord wrote:
To be honest I would be happy with registry entries instead as the
alternative implementations can then add to their installers (or
provide a script) to add the right registry entry.
I'm partial to the config file method myself. I have this vague hope
where this tool could end up being a shebang-script-launching tool for
other scripting languages as well.
That is an explicit non-goal for the launcher - but if it happens to be
able to work that way for you, that's great :)
If you guys (or anyone) would like to agree on some precise rules for
both the location of the config file and its contents and express this
as a patch to the PEP text, I have no problem supporting it in the
implementations. I'd like to insist that the format of the config file
was such that the GetPrivateProfileString() Windows function could be
used to extract the data (eg, only '=' can be used to separate the
name/value pair, case-insensitive and no support for string
interpolation) as I have no interest in writing my own config file
parser in C :)
Cheers,
Mark
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
