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 scoder
Recipients gvanrossum, lukasz.langa, martin.panter, pitrou, rhettinger, scoder, vstinner, yselivanov
Date 2015-04-21.15:44:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429631042.08.0.559354322468.issue24018@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, code usually doesn't fall from the sky with a new CPython release. If something wants to make use of this ABC, it still has to find ways to also work with older CPythons. What would be a good fallback? A backport on PyPI?

I wouldn't even mind shipping this class with Cython and dropping it right into "collections.abc" if it's missing. Cython already contains lots of compatibility code, and we need to patch *something* in all current CPythons either way. Then your code snippet would be the right thing to do for user code (with the twist that Py2.x doesn't have "collections.abc"...).
History
Date User Action Args
2015-04-21 15:44:02scodersetrecipients: + scoder, gvanrossum, rhettinger, pitrou, vstinner, lukasz.langa, martin.panter, yselivanov
2015-04-21 15:44:02scodersetmessageid: <1429631042.08.0.559354322468.issue24018@psf.upfronthosting.co.za>
2015-04-21 15:44:02scoderlinkissue24018 messages
2015-04-21 15:44:01scodercreate