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, steve.dower, tarek
Date 2015-09-03.12:15:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
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 not against developing another module based on appdirs for this.

I do question the usefulness of having such a module in the stdlib,
since I've already gone through a similar experience with the platform
module I wrote several years ago. Ongoing development is not really possible
once a module is in the stdlib and older Python releases don't
benefit from new developments either.

Regarding standard vs. convention: that's all smoke and mirrors :-)
A standard that's not being adopted is not a standard. A convention
may well turn into a standard without ever being written down as
one. A module implementing any such standards or conventions will
have to address more than just one way of doing things in order
to stay compatible with existing software or new developments.
That's what I wanted to say.

But this ticket is not about that discussion anyway...
Date User Action Args
2015-09-03 12:15:42lemburgsetrecipients: + lemburg, barry, georg.brandl, doko, ronaldoussoren, pitrou, tarek, fwierzbicki, ned.deily, glyph, eric.araujo, r.david.murray, michael.foord, flying sheep, martin.panter, steve.dower
2015-09-03 12:15:42lemburglinkissue7175 messages
2015-09-03 12:15:42lemburgcreate