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 r.david.murray
Recipients christian.heimes, georg.brandl, larry, r.david.murray
Date 2013-11-25.12:31:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385382668.16.0.00713883852053.issue19763@psf.upfronthosting.co.za>
In-reply-to
Content
This is a tricky one.  I can see the arguments either way, but it just feels wrong to have future imports in stdlib code.

I personally don't see anything wrong with the import and doctest changes, though.  Sure, someone may come along later and unknowingly break something for your backport, but it isn't likely and IMO it's no big deal if it happens, you can just fix it when your tests fail.  I also don't mind the super call change personally, but that is much more likely to get changed by someone later, since I'm sure other people find it uglier than I do :)

Platform kind of operates under its own rules.  I suppose asyncio does as well :)
History
Date User Action Args
2013-11-25 12:31:08r.david.murraysetrecipients: + r.david.murray, georg.brandl, larry, christian.heimes
2013-11-25 12:31:08r.david.murraysetmessageid: <1385382668.16.0.00713883852053.issue19763@psf.upfronthosting.co.za>
2013-11-25 12:31:08r.david.murraylinkissue19763 messages
2013-11-25 12:31:07r.david.murraycreate