<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 02/08/2010 14:34, Ronald Oussoren wrote:
<blockquote cite="mid:f9203038-f94b-eb28-b9af-d3200dc27db9@me.com"
type="cite">
<div><br>
<br>
On 02 Aug, 2010,at 01:00 PM, Michael Foord
<a class="moz-txt-link-rfc2396E" href="mailto:fuzzyman@voidspace.org.uk"><fuzzyman@voidspace.org.uk></a> wrote:<br>
<span
style="color: rgb(0, 51, 153); font-family: Helvetica,Arial,Verdana,sans-serif;"><span
style="color: rgb(0, 0, 0); font-family: Helvetica,Arial,sans-serif;"><br>
</span></span></div>
<div>
<blockquote type="cite">
<div>
<div class="_stretch">> The only apple one that is actually used
is the .CFUserTextEncoding <br>
> file, I have an .Xcode in my home as well but that is empty and
last <br>
> updated in 2007. AFAIK current versions of Xcode store preferences
in <br>
> ~/Library/Preferences. Most of the other ones are ports of unix
tools <br>
> and store junk in the standard unix location for storing <br>
> configuration. Try edit one without resorting to the command-line<br>
<br>
The configuration files we are discussing are for command line tools - <br>
so I don't think that having to resort to the command line is a <br>
disadvantage at all. If users don't / can't use the command line then <br>
they *won't* want to edit these files anyway.</div>
</div>
</blockquote>
<span> </span></div>
<div>Not being comfortable at the command-line is not the same as not
wanting to edit the global configuration of unittest or distutils.</div>
<div><br>
</div>
</blockquote>
<br>
But both of those are primarily command line tools. A basic ability to
use the command line is a prerequisite of wanting to configure them.<br>
<br>
I would be interested in hearing from other Mac users as to where they
would look for configuration files for command line tools - in ~ or in
~/Library/Preferences?<br>
<br>
Michael<br>
<br>
<blockquote cite="mid:f9203038-f94b-eb28-b9af-d3200dc27db9@me.com"
type="cite">
<div>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?</div>
<div><br>
</div>
<div>
<blockquote type="cite">
<div>
<div class="_stretch"><br>
If they are used to the command line then ~/.python32/distutils.cfg is <br>
going to be a very natural place for them.</div>
</div>
</blockquote>
<span> </span></div>
<div>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.</div>
<div><br>
</div>
<div>The MacOSX conventions are described here
<a class="moz-txt-link-rfc2396E" href="http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFileSystem/BPFileSystem.html#//apple_ref/doc/uid/10000185-SW1"><http://developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPFileSystem/BPFileSystem.html#//apple_ref/doc/uid/10000185-SW1></a>.</div>
<div><br>
</div>
<div>Macosx-is-not-a-crappy-linux-ly yours,</div>
<div><br>
</div>
<div> Ronald</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.ironpythoninaction.com/">http://www.ironpythoninaction.com/</a>
<a class="moz-txt-link-freetext" href="http://www.voidspace.org.uk/blog">http://www.voidspace.org.uk/blog</a>
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
</pre>
</body>
</html>