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 eric.snow
Recipients dino.viehland, eric.snow, methane, serhiy.storchaka
Date 2019-05-30.19:43:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559245398.39.0.86697715856.issue36839@roundup.psfhosted.org>
In-reply-to
Content
FWIW, I don't see the problem with supporting any read-only "buffer" object, rather than just bytes objects, for the string of bytes in a code object.  That's all that Dino is proposing.  The change is not invasive and solves a real need.  The additional maintenance burden is negligible.  Furthermore, the accommodation makes sense conceptually.
History
Date User Action Args
2019-05-30 19:43:18eric.snowsetrecipients: + eric.snow, dino.viehland, methane, serhiy.storchaka
2019-05-30 19:43:18eric.snowsetmessageid: <1559245398.39.0.86697715856.issue36839@roundup.psfhosted.org>
2019-05-30 19:43:18eric.snowlinkissue36839 messages
2019-05-30 19:43:18eric.snowcreate