On Wed, Mar 23, 2011 at 8:14 PM, Mark Hammond <mhammond at skippinet.com.au> wrote: > 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 :) In the user directory much like TortoiseHG adds a murcurial.ini file to the users directory for basic globa config the launch could look for a python.ini there and use to to add known paths or version overrides on a user by user basis.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4