[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Éric Araujo added the comment: FWIW, I’m no longer strongly advocating using $XDG_CONFIG_HOME, since it seems to have little acceptance outside of graphical applications. Using it *or* ~/.python (or ~/.pythonx.y) would work for me. Since this seems like a big change for no benefit in distutil

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Glyph Lefkowitz added the comment: > Well, that makes it the user-specific equivalent of /usr or /usr/local. > Do you put your configuration files in /usr/local ? Why put them > in .local ? Yes, software built for /usr/local will often respect /usr/local/etc in addition to /etc. Also, many de

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Michael Foord added the comment: I still think that user editable configuration data, at least on windows, is different from application data. It would definitely seem weird to me to have a config file in the %APPDATA% directory. %APPDATA% would be fine for a cache or other application specif

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Éric Araujo added the comment: Pointed out by Tarek: http://github.com/ActiveState/appdirs#readme (shame it doesn‘t follow the BaseDir Spec on Free OSes). -- ___ Python tracker

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Éric Araujo added the comment: I guess I misremembered. %APPDATA% is /usr/share, right? What I meant was the variable that expands to the “documents and settings” directory. -- ___ Python tracker _

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Michael Foord added the comment: 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. --

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Éric Araujo added the comment: When ~/.local/lib was chosen for the user directory, the BaseDir Spec was given as prior example. Why not go the full way and follow the spec? The config file could be $XDG_CONFIG_HOME/python/distutils, with $XDG_CONFIG_HOME defaulting to ~/.config. References: ht

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Ronald Oussoren added the comment: I agree with Ned that neither ~/.local nor /etc are a good fit for OSX, sadly enough I wasn't paying attention when ~/.local was added as python already had a per-user directory on OSX: ~/Library/Python. The common unix directories are often not a good pick

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Changes by Frank Wierzbicki : -- nosy: +fwierzbicki ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Ned Deily added the comment: I don't think there's a misunderstanding. By "putting", I meant "reading" or "writing". IMO, /etc is not the place on OS X to be looking for python-related configuration files, certainly not for framework installs. Likewise for ~/.python and ~/.local. Unfortun

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Marc-Andre Lemburg added the comment: Ned Deily wrote: > > Ned Deily added the comment: > > /etc is definitely not the right place to put files for OS X framework > builds; if necessary, an etc directory could be added under the > framework version directory as a sibling of bin and lib. It

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Ned Deily added the comment: /etc is definitely not the right place to put files for OS X framework builds; if necessary, an etc directory could be added under the framework version directory as a sibling of bin and lib. It's also very un-OS X like to be putting things into ~/.python and ~/.

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Michael Foord added the comment: Noting of course that on IronPython it should be: %APPDATA%/IronPython/PythonX.Y/ or wherever we decided in the end. :-) -- ___ Python tracker _

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Michael Foord added the comment: For Linux and Mac OS X put the config file wherever the 'right' place is then, but we are starting to create a lot of new directories disparate from the actual install. Oh well. On Windows we create: %APPDATA%/Python/PythonX.Y/site-packages If it is to no longe

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Georg Brandl added the comment: But ~/.local is simply not the location for config files. -- ___ Python tracker ___ ___ Python-bugs-li

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Michael Foord added the comment: Personally I'm uncomfortable with creating yet-another-location-for-config-files. As we now have is ~/.local/pythonX.Y I would reuse this. -- ___ Python tracker ___

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Tarek Ziadé added the comment: Thanks for the info Georges. I am adding Matthias and Michael so they can give us their opinions for their platforms (Debian/Ubuntu and Win) -- nosy: +doko, michael.foord ___ Python tracker

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Georg Brandl added the comment: FYI, /etc/pythonX.Y (and /etc/python) are used by Debian; the former contains site.py and sitecustomize.py, the latter a file called debain_config. I can't see how this could become a problem, but maybe someone else does. -- nosy: +georg.brandl

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Tarek Ziadé added the comment: The subversion system looks pretty nice ! So here's a modified proposal that covers the python version as well. = per user configuration files = ~/.pythonMAJOR.MINOR Examples: ~/.python2.7 ~/.python3.1 On Windows, ~ will be replaced by APPDATA if founded in

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Marc-Andre Lemburg added the comment: Tarek Ziadé wrote: > > Tarek Ziadé added the comment: > > I like ~/.python very much too (that was my initial proposal IIRC). +1 on that name as well. One thing to note though: it is well possible that a user uses multiple Python versions. With just on

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Tarek Ziadé added the comment: I like ~/.python very much too (that was my initial proposal IIRC). I guess the best way to add this support is to provide a new api in site.py, that returns this folder. Distutils can move pypirc and distutils.cfg file there. Now for the global distutils.cfg,

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Antoine Pitrou added the comment: > The distutils.cfg file is located in the distutils package itself ! > > So the target is ~/.local/pythonX.X/site-packages/distutils/distutils.cfg Ah, that's horrible. -1 to that. Configuration files should be easily findable by skimming through the dot-files

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Tarek Ziadé added the comment: > Well, that makes it the user-specific equivalent of /usr or /usr/local. > Do you put your configuration files in /usr/local ? > Why put them in .local ? The distutils.cfg file is located in the distutils package itself ! So the target is ~/.local/pythonX.X/sit

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

R. David Murray added the comment: +1 to what Antoine said. -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list maili

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Antoine Pitrou added the comment: I've read the thread now and I think the original proposal of having a ~/.python was more sensible and more user-friendly. -- ___ Python tracker ___

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Antoine Pitrou added the comment: > That's what is returned by site.getuserbase() > > (which uses PYTHONUSERBASE, and defaults to ~/.local) Well, that makes it the user-specific equivalent of /usr or /usr/local. Do you put your configuration files in /usr/local ? Why put them in .local ? > PY

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Tarek Ziadé added the comment: That's what is returned by site.getuserbase() (which uses PYTHONUSERBASE, and defaults to ~/.local) PYTHONUSERBASE is the root of Python user-specific paths so it makes sense to have all Python related files in there. This came up with the discussion we had with

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

Antoine Pitrou added the comment: Why is this? .local/ contains machine-installed files while .pydistutils.cfg is edited by the user. -- nosy: +pitrou ___ Python tracker ___

[issue7175] unify pydistutils.cfg and distutils.cfg and use .local

New submission from Tarek Ziadé : [.]pydistutils.cfg will be deprecated in favor of a single "distutils.cfg", located in .local/ alongside the files added for example by the per user-site packages. -- assignee: tarek components: Distutils messages: 94272 nosy: tarek priority: normal seve