[issue14198] Backport parts of the new memoryview documentation

Stefan Krah report at bugs.python.org
Mon Mar 5 10:30:16 CET 2012

New submission from Stefan Krah <stefan-usenet at bytereef.org>:

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 doesn't behave nicely in those versions, so we'd be violating our own guidelines.

Perhaps the relevant sections should be updated with a reference saying that the semantics have been cleaned up in 3.3, and if in doubt, try to follow the 3.3 documentation?"

assignee: skrah
components: Documentation
messages: 154934
nosy: ncoghlan, pitrou, skrah
priority: normal
severity: normal
status: open
title: Backport parts of the new memoryview documentation
type: enhancement
versions: Python 2.7, Python 3.1, Python 3.2

Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list