On 24/03/2011 00:44, Dj Gilcrease wrote: > 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. A single global location (for shared installs) or a single per-user location for per-user installs would seem to be sensible if the config file route is chosen. All the best, Michael Foord > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
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