On 02 Aug, 2010,at 01:00 PM, Michael Foord <fuzzyman at voidspace.org.uk> wrote: > The only apple one that is actually used is the .CFUserTextEncoding > file, I have an .Xcode in my home as well but that is empty and last > updated in 2007. AFAIK current versions of Xcode store preferences in > ~/Library/Preferences. Most of the other ones are ports of unix tools > and store junk in the standard unix location for storing > configuration. Try edit one without resorting to the command-line The configuration files we are discussing are for command line tools - so I don't think that having to resort to the command line is a disadvantage at all. If users don't / can't use the command line then they *won't* want to edit these files anyway. Not being comfortable at the command-line is not the same as not wanting to edit the global configuration of unittest or distutils. Anyway, does that mean that the configuration should move if I create a patch for IDLE that allows you the manage the unittest configuration through a GUI? If they are used to the command line then ~/.python32/distutils.cfg is going to be a very natural place for them. That location isn't natural for me. If we invent a new location for python-related configuration file we might as well do it properly and follow platform conventions. The MacOSX conventions are described here <http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFileSystem/BPFileSystem.html#//apple_ref/doc/uid/10000185-SW1>. Macosx-is-not-a-crappy-linux-ly yours, Ronald -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100802/36396a3d/attachment.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