➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2012-09-10 21:54 by ellery.newcomer, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| test.c | ellery.newcomer, 2012-09-10 21:54 | example code calling PyObject_CheckBuffer on an array.array object | ||
| Messages (4) | |||
|---|---|---|---|
| msg170242 - (view) | Author: Ellery Newcomer (ellery.newcomer) | Date: 2012-09-10 21:54 | |
According to http://docs.python.org/library/array.html, array.array supports the buffer interface; however in python 2.7, PyObject_CheckBuffer says this is not the case. all is well in python 3.2, though. |
|||
| msg170244 - (view) | Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2012-09-10 22:54 | |
array.array supports the old buffer interface not the new one, which PyObject_CheckBuffer is part of. |
|||
| msg170247 - (view) | Author: Ellery Newcomer (ellery.newcomer) | Date: 2012-09-10 23:20 | |
relevant question, then, is why does array not support the new buffer interface while str and bytearray support both old and new? |
|||
| msg170248 - (view) | Author: Benjamin Peterson (benjamin.peterson) * |
Date: 2012-09-10 23:23 | |
It simply wasn't converted in time for the 2.7 release. The new buffer API is considered something of a technical preview in Python 2.x. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:35 | admin | set | github: 60119 |
| 2012-09-10 23:23:08 | benjamin.peterson | set | messages: + msg170248 |
| 2012-09-10 23:20:06 | ellery.newcomer | set | messages: + msg170247 |
| 2012-09-10 22:54:32 | benjamin.peterson | set | status: open -> closed nosy: + benjamin.peterson messages: + msg170244 resolution: not a bug |
| 2012-09-10 22:00:29 | vstinner | set | nosy:
+ skrah |
| 2012-09-10 21:54:06 | ellery.newcomer | create | |