[issue7175] Define a standard location and API for configuration files

Éric Araujo added the comment: This ticket did not reach a consensus. It seems there would be little value in changing the existing scheme for IDLE and such; external tools can (and often do) already use appdirs; I suggest closing this. -- ___

[issue7175] Define a standard location and API for configuration files

Change by Ronald Oussoren : -- nosy: -ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7175] Define a standard location and API for configuration files

flying sheep added the comment: just because people do something doesn’t mean it’s right. i guess the tendency for CLI applications to do it wrong comes from 1. their ad-hoc beginnings. you usually start with one script file and extend it 2. availability expanduser('~') is in the stdlib and

[issue7175] Define a standard location and API for configuration files

Changes by Michael Foord : -- nosy: -michael.foord ___ Python tracker ___ ___

[issue7175] Define a standard location and API for configuration files

R. David Murray added the comment: The "tendency of CLI applications to do it wrong" comes from the fact that they are following the *older* unix (de-facto) standard, which is to put config files in the home directory as dot files. That is, they are *not* doing it wrong, they are following

[issue7175] Define a standard location and API for configuration files

Marc-Andre Lemburg added the comment: On 02.09.2015 16:37, flying sheep wrote: > > hi mark, i’ve just lengthily replied to you on python-ideas. > > in short: nope! many command line tools that are relatively new (among them > your examples git and pip) honor the specs, my ~/.cache, ~/.config,

[issue7175] Define a standard location and API for configuration files

Marc-Andre Lemburg added the comment: On 03.09.2015 13:37, flying sheep wrote: > all three OSs have stable, widely followed standards in place, and the idea > of providing a python stdlib API for them received an almost unanimously > positive response – with the sole exception being you. I'm

[issue7175] Define a standard location and API for configuration files

flying sheep added the comment: you’re right about the two problems being mixed, however not about the standards. also you’re intermingling conventions with actual standards. the directory standards for all three big OSs are either not going to change or fitted with a backwards-compatibility

[issue7175] Define a standard location and API for configuration files

flying sheep added the comment: of course if there is a chance that some specific config file exists at a known location, it’s the only sane choice to try and look for it there iff it isn’t in its preferred location. e.g. fontconfig made that switch some time ago: it used to be ~/.fonts.conf,

[issue7175] Define a standard location and API for configuration files

Marc-Andre Lemburg added the comment: The XDG standard seems to focus on desktop GUI applications and that's also where it's mostly used. Python has it's own installation scheme, which is documented at the top of sysconfig.py and which we've had ever since distutils became part of the stdlib.

[issue7175] Define a standard location and API for configuration files

Changes by Steve Dower : -- nosy: +steve.dower ___ Python tracker ___ ___

[issue7175] Define a standard location and API for configuration files

flying sheep added the comment: hi mark, i’ve just lengthily replied to you on python-ideas. in short: nope! many command line tools that are relatively new (among them your examples git and pip) honor the specs, my ~/.cache, ~/.config, and ~/.local/share is full of things belonging to

[issue7175] Define a standard location and API for configuration files

Barry A. Warsaw added the comment: On Sep 01, 2015, at 07:15 PM, Glyph Lefkowitz wrote: >There are other advantages to following the XDG spec. If we follow it >correctly (and not, like Barry suggested, start adding random other >directories like ~/.python) I was really just suggesting reading

[issue7175] Define a standard location and API for configuration files

Glyph Lefkowitz added the comment: XDG_CONFIG_HOME is not generally set to anything; the default of ~/.config is usually fine. However, the point is that you _can_ set it to point at a different location. The relevant specification is here:

[issue7175] Define a standard location and API for configuration files

flying sheep added the comment: no, sorry, but ~/.python is wrong on linux. there exists a standard about where things belong: http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html it says that configuration stuff belongs into `XDG_CONFIG_HOME`, with a fallback to

[issue7175] Define a standard location and API for configuration files

Barry A. Warsaw added the comment: I'm of mixed opinion. I personally don't like cluttering up my $HOME with a jillion dotfiles so I appreciate the organization XDG_CONFIG_HOME offers. But that also makes things less discoverable. Looking in XDG_CONFIG_HOME first with a fallback to $HOME

[issue7175] Define a standard location and API for configuration files

Antoine Pitrou added the comment: If this is about existing config files, then we should make sure we don't break existing installations. Also, multiple possible locations in the home dir are confusing. If this is about new config files, then ~/.config/python/XXX is probably ok. I'm not sure

[issue7175] Define a standard location and API for configuration files

R. David Murray added the comment: That standard is just wrong, dotfiles belong in $HOME :) I'm only half joking, having grown up with Unix and having had the experience of flailing around for a while before I figured out a particular program's rc file was in .config instead of where I

[issue7175] Define a standard location and API for configuration files

Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7175 ___ ___ Python-bugs-list

[issue7175] Define a standard location and API for configuration files

Éric Araujo mer...@netwok.org added the comment: See also #12393. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7175 ___ ___ Python-bugs-list

[issue7175] Define a standard location and API for configuration files

Éric Araujo mer...@netwok.org added the comment: The issue proved more complicated than expected, due to antics of Mac OS X and Windows Vista, so I set it aside for later. I intend to summarize all useful comments from the python-dev thread and bug reports comments and try to reach agreement

[issue7175] Define a standard location and API for configuration files

Barry A. Warsaw ba...@python.org added the comment: I'm mildly uncomfortable advocating many different new dot directories in $HOME (e.g. .python2.7 .python3.1 .python3.2). Let's say -0. Also, because of backward compatibility, I think most configuration files will end up being similar

[issue7175] Define a standard location and API for configuration files

Glyph Lefkowitz gl...@twistedmatrix.com added the comment: I would still prefer ~/.local/something-parallel-to-where-it's-usually-installed for its ease of documentation. But ~/.python/X.Y isn't terribly objectionable. A minor point about Michael Foord's fallback proposal: I don't know why

[issue7175] Define a standard location and API for configuration files

Glyph Lefkowitz gl...@twistedmatrix.com added the comment: I agree with Michael Foord; my comment on issue 8404 http://bugs.python.org/issue8084#msg122935 may be of interest to anyone looking at this as well. -- ___ Python tracker

[issue7175] Define a standard location and API for configuration files

Michael Foord mich...@voidspace.org.uk added the comment: It would be nice to settle this. Personally I would like to see the defaults being: Linux: ~/.pythonx.y Mac OS X: ~/.pythonx.y with a fallback of ~/Library/Preferences/.pythonx.y Windows: ~/pythonx.y perhaps with a backup of

[issue7175] Define a standard location and API for configuration files

Éric Araujo mer...@netwok.org added the comment: I’m retitling the bug, given its broader scope. Michael Foord added another stdlib example: IDLE config files. Python-dev thread: http://mail.python.org/pipermail/python-dev/2010-August/103011.html -- assignee: tarek - components: