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 steve.dower
Recipients dstufft, jaraco, lukasz.langa, ned.deily, steve.dower
Date 2020-06-09.08:25:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
That was a *big* patch to importlib.resources... And newly defined and standardised protocols? That seems like a lot to bring in without having gone through a PEP anyway, despite the minor bug that has drawn attention to it.

I don't think backports should be treated as incubators for standard modules, getting new features that then flow directly into the stdlib. It's fine to have a fork for incubation, but people need to rely on consistency in stdlib and backports.

All that to say, I think we should revert the importlib changes *anyway*, and also because there's something wrong with them right now.
Date User Action Args
2020-06-09 08:25:48steve.dowersetrecipients: + steve.dower, jaraco, ned.deily, lukasz.langa, dstufft
2020-06-09 08:25:48steve.dowersetmessageid: <>
2020-06-09 08:25:48steve.dowerlinkissue40924 messages
2020-06-09 08:25:48steve.dowercreate