[issue14198] Backport parts of the new memoryview documentation

Stefan Krah added the comment: This is actually a lot of work, I don't think I'll have time for it. Please just reopen if you think there's a chance that someone will take the task. -- resolution: -> wont fix stage: -> resolved status: open -> closed

[issue14198] Backport parts of the new memoryview documentation

Changes by Stefan Krah : -- assignee: skrah -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue14198] Backport parts of the new memoryview documentation

Changes by Nick Coghlan : -- versions: -Python 3.1, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14198] Backport parts of the new memoryview documentation

Stefan Krah added the comment: Kristj??n Valur J??nsson wrote: > Stefan, I just want to point out this issue, if you are touching 2.7: > http://bugs.python.org/issue10538 > Do you think it merits being fixed? I think so. A patch would be appreciated, since the issue touches the old buffer inte

[issue14198] Backport parts of the new memoryview documentation

Kristján Valur Jónsson added the comment: Stefan, I just want to point out this issue, if you are touching 2.7: http://bugs.python.org/issue10538 Do you think it merits being fixed? -- nosy: +krisvale ___ Python tracker

[issue14198] Backport parts of the new memoryview documentation

New submission from Stefan Krah : Nick's comment from #10181: "It occurs to me that one thing that *could* be backported to early versions are some of the documentation improvements on how to correctly handle the lifecycle of fields in Py_buffer. That gets messy though because memoryview does