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 Arfrever, Denis.Bilenko, alex, barry, benjamin.peterson, christian.heimes, dstufft, giampaolo.rodola, janssen, lemburg, pitrou
Date 2014-11-07.10:08:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1415354883.12.0.083099172568.issue22438@psf.upfronthosting.co.za>
In-reply-to
Content
Even though it may have been considered a private API (*), users certainly won't understand that their application just broke because of a Python patch level release upgrade, so if possible, I think the API should be added back and flagged as "private, but used by at least eventlet and gevent".

Alternatively: Why not add it back and make it an officially documented API ?

(*) The API is missing the leading underscore, so it's not really private by our usual conventions, it's just undocumented.
History
Date User Action Args
2014-11-07 10:08:03lemburgsetrecipients: + lemburg, barry, janssen, pitrou, giampaolo.rodola, christian.heimes, benjamin.peterson, Arfrever, alex, Denis.Bilenko, dstufft
2014-11-07 10:08:03lemburgsetmessageid: <1415354883.12.0.083099172568.issue22438@psf.upfronthosting.co.za>
2014-11-07 10:08:03lemburglinkissue22438 messages
2014-11-07 10:08:02lemburgcreate