This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients barry, doko, eric.araujo, flying sheep, fwierzbicki, georg.brandl, glyph, lemburg, martin.panter, michael.foord, ned.deily, pitrou, r.david.murray, ronaldoussoren, tarek
Date 2015-09-02.10:49:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 and which we've had ever since distutils became part of the stdlib.

For user installs, this bases all installations under the PYTHONUSERBASE dir, which defaults to ~/.local/ on Unix.

So user installs go into ~/.local/pythonX.X/ (I also have a ~/.local/python/X.X/ - not sure where that came from).

Python also uses ~/.pypirc for PyPI, ~/.python-eggs for setuptools, ~/.python_history for readline history.

The installation scheme currently doesn't define a dir for config files, only for "data" files, so adding one would probably be wise.

Since we already own ~/.local/pythonX.X/, why not put config files in there ?

For some extra Unix touch, we could use ~/.local/pythonX.X/etc/ and then move the cache bits to a ./var/ subdir (by defining another new "cache" entry for the schemes).
Date User Action Args
2015-09-02 10:49:41lemburgsetrecipients: + lemburg, barry, georg.brandl, doko, ronaldoussoren, pitrou, tarek, fwierzbicki, ned.deily, glyph, eric.araujo, r.david.murray, michael.foord, flying sheep, martin.panter
2015-09-02 10:49:41lemburgsetmessageid: <>
2015-09-02 10:49:41lemburglinkissue7175 messages
2015-09-02 10:49:40lemburgcreate