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 benjamin.peterson, bkabrda, flavio, matteo, ncoghlan, pitrou, rkuska, vstinner
Date 2015-09-15.10:08:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1442311721.96.0.539747182722.issue25084@psf.upfronthosting.co.za>
In-reply-to
Content
For the sake of folks writing single-source code, and needing to support Python 2.7 for at least as long as we're supporting it upstream, I believe it would be beneficial to have consistency here.

For those that didn't follow the Fedora/RHEL issue chain, the original Fedora 19 bug report was https://bugzilla.redhat.com/show_bug.cgi?id=917709 and the corresponding "won't fix" upstream issue was issue 17748.

Unfortunately, in addition to only helping in a subset of cases, the workaround we applied also extends the affected APIs in an undocumented way that's incompatible with the Python 3 changes to the same API, so I've suggested that regardless of the verdict upstream, we should bring the API extension into line with Python 3 downstream.
History
Date User Action Args
2015-09-15 10:08:42ncoghlansetrecipients: + ncoghlan, pitrou, vstinner, benjamin.peterson, bkabrda, rkuska, flavio, matteo
2015-09-15 10:08:41ncoghlansetmessageid: <1442311721.96.0.539747182722.issue25084@psf.upfronthosting.co.za>
2015-09-15 10:08:41ncoghlanlinkissue25084 messages
2015-09-15 10:08:41ncoghlancreate