Issue 19666: Format string for ASCII unicode or bytes-like object as readonly buffer (original) (raw)

Issue19666

➜

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.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/63865

classification

process

Created on 2013-11-20 18:14 by christian.heimes, last changed 2022-04-11 14:57 by admin.

Messages (5)
msg203516 - (view)	Author: Christian Heimes (christian.heimes) *	Date: 2013-11-20 18:14
I could use a format string for either ASCII unicode or bytes buffer in a few places, e.g. a* (bytes, bytearray, bytes-like object or ASCII unicode) [Py_buffer] Like y* it should handle PyBUF_SIMPLE with 'C' contiguous but it should only accept one dimensional buffers. In case the object is an ASCII PyUnicode_Object it should return its ASCII data as Py_buffer.
msg203518 - (view)	Author: Antoine Pitrou (pitrou) *	Date: 2013-11-20 18:20
It seems this would add a dependency to the unicode implementation (other unicode representations may not allow you to take a Py_buffer to the ASCII data).
msg203617 - (view)	Author: STINNER Victor (vstinner) *	Date: 2013-11-21 11:55
Where do you plan to use this new format? Can you please give examples? > (other unicode representations may not allow you to take a Py_buffer to the ASCII data). Py_buffer and PyArg_ParseTuple() are very specific to CPython.
msg345078 - (view)	Author: Batuhan Taskaya (BTaskaya) *	Date: 2019-06-09 09:38
Don't we need to discuss it more before triage it as "patch required"?
msg345180 - (view)	Author: Gregory P. Smith (gregory.p.smith) *	Date: 2019-06-11 04:57
"needs patch" doesn't mean it has been accepted, it's just a common state for issues where nobody has written any code even as a proof of concept. Christian - is this still desired?