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 skrah
Recipients benjamin.peterson, dw, hynek, kmike, pitrou, scoder, serhiy.storchaka, skrah, stutzbach
Date 2014-07-21.16:23:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1405959781.5.0.807342255927.issue22003@psf.upfronthosting.co.za>
In-reply-to
Content
The original wording in the PEP is this:

readonly
--------
    an integer variable to hold whether or not the memory is readonly. 1
    means the memory is readonly, zero means the memory is writable.


To me this means that a hypothetical compiler that could figure
out at compile time that the readonly flag is set would be allowed
to put the buffer contents into the read-only data section.
History
Date User Action Args
2014-07-21 16:23:01skrahsetrecipients: + skrah, pitrou, scoder, benjamin.peterson, stutzbach, hynek, dw, serhiy.storchaka, kmike
2014-07-21 16:23:01skrahsetmessageid: <1405959781.5.0.807342255927.issue22003@psf.upfronthosting.co.za>
2014-07-21 16:23:01skrahlinkissue22003 messages
2014-07-21 16:23:01skrahcreate