[Python-Dev] proto-pep: plugin proposal (for unittest)
Michael Foord
fuzzyman at voidspace.org.uk
Sun Aug 1 20:50:46 CEST 2010
On 01/08/2010 18:38, R. David Murray wrote:
> On Sun, 01 Aug 2010 17:22:55 +0200,<merwok at netwok.org> wrote:
>
>>> Speaking of which... Your documentation says it's named ~/unittest.cfg,
>>> could you make this a file in the user base (that is, the prefix where
>>> 'setup.py install --user' will install files)?
>>>
>> Putting .pydistutils.cfg .pypirc .unittest2.cfg .idlerc and possibly
>> other in the user home directory (or %APPDATA% on win32 and
>> what-have-you on Mac) is unnecessary clutter. However, $PYTHONUSERBASE
>> is not the right directory for configuration files, as pointed in
>> http://bugs.python.org/issue7175
>>
>> It would be nice to agree on a ~/.python (resp. %APPADATA%/Python) or
>> $XDG_CONFIG_HOME/python directory and put config files there.
>>
> +1
>
> Certainly ~/unittest.cfg is the wrong name for unix (it doesn't start
> with a '.'), and certainly the location is OS specific.
>
> Anyone who cares about config file locations should read issue 7175.
>
I'm happy to choose a location / name based on consensus. There doesn't
seem to be any consensus yet. As a (mainly ex) windows user I would hate
to have user editable data in APPDATA as it is not a location the user
ever expects to visit. The home directory, or a subdirectory thereof,
for user editable app specific data is more usual and more friendly.
All the best,
Michael Foord
> --
> R. David Murray www.bitdance.com
> _______________________________________________
> 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.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
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.
More information about the Python-Dev
mailing list