Message249527
| Author |
flying sheep |
| 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日.08:27:05 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1441182426.23.0.993792531669.issue7175@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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, now it’s ${XDG_CONFIG_HOME-$HOME/.config}/fontconfig/fonts.conf
the library will look at the new position and if it can’t find anything there, it looks at the old one.
but for new config files we should follow standards. on windows and OSX there are different ones: see the current discussion on python-ideas for specifics and problems. but on linux the only standard for this which i know is XDG-base-directories, so we should follow that for new config files. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年09月02日 08:27:06 | flying sheep | set | recipients:
+ flying sheep, lemburg, barry, georg.brandl, doko, ronaldoussoren, pitrou, tarek, fwierzbicki, ned.deily, glyph, eric.araujo, r.david.murray, michael.foord, martin.panter |
| 2015年09月02日 08:27:06 | flying sheep | set | messageid: <1441182426.23.0.993792531669.issue7175@psf.upfronthosting.co.za> |
| 2015年09月02日 08:27:06 | flying sheep | link | issue7175 messages |
| 2015年09月02日 08:27:05 | flying sheep | create |
|