[Python-Dev] Slice as a copy... by design? (original) (raw)
Stefan Behnel stefan_ml at behnel.de
Thu May 22 20:39:06 CEST 2008
- Previous message: [Python-Dev] Slice as a copy... by design?
- Next message: [Python-Dev] Slice as a copy... by design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Isaac Morland wrote:
On Thu, 22 May 2008, Christian Heimes wrote:
The buffer interface was designed for the slice-as-copy use case:
a = "abcdefg" b = buffer(a, 2, 3) b <read-only buffer for 0x839c2e0, size 3, offset 2 at 0x8391c40> str(b) 'cde' [....] This answers my musing about shared slices. But it points me at another question: why is buffer() listed in "Non-essential Built-in Functions"? While it is obviously not essential like str() or list(), it isn't deprecated like apply().
Even worse, it's gone in Py3:
Python 3.0a5 (r30a5:62856, May 9 2008, 11:26:14) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type "help", "copyright", "credits" or "license" for more information.
buffer Traceback (most recent call last): File "", line 1, in NameError: name 'buffer' is not defined
Stefan
- Previous message: [Python-Dev] Slice as a copy... by design?
- Next message: [Python-Dev] Slice as a copy... by design?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]