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 Arfrever, BreamoreBoy, christian.heimes, jcea, martin.panter, sbt, skrah
Date 2015-10-31.15:05:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
> But I think there should be some way of guaranteeing that a memoryview will not try to access memory which has already been freed.

Unless the "buffered *self" parameter in _buffered_raw_read() is
made a full PEP-3118 exporter, I'm not sure how it would be possible
to prevent all examples of this kind.
History
Date User Action Args
2015-10-31 15:05:22skrahsetrecipients: + skrah, jcea, christian.heimes, Arfrever, BreamoreBoy, sbt, martin.panter
2015-10-31 15:05:22skrahsetmessageid: <[email protected]>
2015-10-31 15:05:22skrahlinkissue15994 messages
2015-10-31 15:05:22skrahcreate