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 gvanrossum
Recipients gvanrossum, rhettinger, serhiy.storchaka
Date 2016-05-06.15:47:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462549659.16.0.797454242097.issue25628@psf.upfronthosting.co.za>
In-reply-to
Content
And by "safely" I mean that I don't mind if some code breaks when they upgrade to a new feature release.

FWIW the code most likely to break is code that wraps these functions with an identical interface.
History
Date User Action Args
2016-05-06 15:47:39gvanrossumsetrecipients: + gvanrossum, rhettinger, serhiy.storchaka
2016-05-06 15:47:39gvanrossumsetmessageid: <1462549659.16.0.797454242097.issue25628@psf.upfronthosting.co.za>
2016-05-06 15:47:39gvanrossumlinkissue25628 messages
2016-05-06 15:47:39gvanrossumcreate