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 methane
Recipients dino.viehland, eric.snow, methane
Date 2019-05-29.03:15:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559099714.39.0.790387848404.issue36839@roundup.psfhosted.org>
In-reply-to
Content
> Could someone create a buffer object which still allows the underlying memory to be written?  Sure.  But I can use ctypes to modify byte code today as well with something like "ctypes.cast(id(f.__code__.co_code) + 32, ctypes.POINTER(ctypes.c_char)) [0] = 101" 

You are comparing apple and orange.
Breanking memory inside immutable object by ctypes is far different from mutating mutable memory.

It introduce more weakness and complexity into code object.

At least, you need to demonstrate the benefit.

When importing module, there are many objects are created.  Why avoiding decref only for co_code make much difference?
History
Date User Action Args
2019-05-29 03:15:14methanesetrecipients: + methane, dino.viehland, eric.snow
2019-05-29 03:15:14methanesetmessageid: <1559099714.39.0.790387848404.issue36839@roundup.psfhosted.org>
2019-05-29 03:15:14methanelinkissue36839 messages
2019-05-29 03:15:14methanecreate