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 denilsonsa
Recipients Arfrever, amaury.forgeotdarc, denilsonsa, eric.araujo, giampaolo.rodola, loewis, neologix, pitrou, rosslagerwall, vstinner, zbysz
Date 2012-01-22.00:20:01
SpamBayes Score 2.6746938e-12
Marked as misclassified No
Message-id <>
In-reply-to <>
On Sat, Jan 21, 2012 at 17:40, Giampaolo Rodola' <> wrote:
> Given the different opinions about the API, I think it's best to expose the lowest
> level functionality as-is, and let the user decide what to do (read env vars first,
> suppress the exception, use a fallback, etc.).

As a Python user (and not a committer), I disagree.

As an user, I don't care too much where the function should be placed
(although I believe os or sys are sensible choices). What I do care is
that I want a extremely simple function that will "just work". Don't
make me add code for handling all the extra cases, such code should be
inside the function.

All this discussion about the API made me remember this presentation:

Also, I see no downside of using a Named Tuple. Issue 4285 actually
added a named tuple to the sys.version_info.
Date User Action Args
2012-01-22 00:20:02denilsonsasetrecipients: + denilsonsa, loewis, amaury.forgeotdarc, pitrou, vstinner, giampaolo.rodola, eric.araujo, Arfrever, zbysz, neologix, rosslagerwall
2012-01-22 00:20:02denilsonsalinkissue13609 messages
2012-01-22 00:20:01denilsonsacreate