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 ncoghlan
Recipients JelleZijlstra, giampaolo.rodola, ncoghlan, rhettinger, yselivanov
Date 2017-03-03.04:00:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488513608.73.0.803191927972.issue29679@psf.upfronthosting.co.za>
In-reply-to
Content
Something that occurred to me as being a bit tricky to handle here is the backport to contextlib2: that maintains compatibility with 2.6+, so it would need to split any code using "async def" and "await" out to a separate file that only gets imported on 3.5+ (and similarly only run the corresponding test cases on 3.5+).

A potentially simpler alternative to that would be to create a new "backports.contextlib" package that only supports 3.5+ and explicitly restrict contextlib2 itself to code that runs in the common subset of Python 2 & 3.
History
Date User Action Args
2017-03-03 04:00:08ncoghlansetrecipients: + ncoghlan, rhettinger, giampaolo.rodola, yselivanov, JelleZijlstra
2017-03-03 04:00:08ncoghlansetmessageid: <1488513608.73.0.803191927972.issue29679@psf.upfronthosting.co.za>
2017-03-03 04:00:08ncoghlanlinkissue29679 messages
2017-03-03 04:00:08ncoghlancreate