Message253796
| 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 | <1446303922.14.0.398015497259.issue15994@psf.upfronthosting.co.za> |
| 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:22 | skrah | set | recipients: + skrah, jcea, christian.heimes, Arfrever, BreamoreBoy, sbt, martin.panter |
| 2015-10-31 15:05:22 | skrah | set | messageid: <1446303922.14.0.398015497259.issue15994@psf.upfronthosting.co.za> |
| 2015-10-31 15:05:22 | skrah | link | issue15994 messages |
| 2015-10-31 15:05:22 | skrah | create | |