Message170638
| Author | skrah |
|---|---|
| Recipients | amaury.forgeotdarc, jcea, pitrou, sbt, skrah |
| Date | 2012-09-18.08:33:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1347957234.96.0.969752587733.issue15903@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
So the problem is that readinto(view) might result in several references to view? I don't think that can be solved on the memoryview side. One could do: view = PyMemoryView_FromObject(b); // Lie about writability ((PyMemoryViewObject *)view)->view.readonly = 0; [...] Then the view owns a reference to the bytes object. But that does not solve the problem that writable memoryviews based on a readonly object might be hanging around. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-09-18 08:33:55 | skrah | set | recipients: + skrah, jcea, amaury.forgeotdarc, pitrou, sbt |
| 2012-09-18 08:33:54 | skrah | set | messageid: <1347957234.96.0.969752587733.issue15903@psf.upfronthosting.co.za> |
| 2012-09-18 08:33:54 | skrah | link | issue15903 messages |
| 2012-09-18 08:33:53 | skrah | create | |