Message 98050 - Python tracker

➜

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.

In-reply-to
Author	ghaering
Recipients	flox, ghaering, lemburg, pitrou
Date	2010年01月19日.10:07:52
SpamBayes Score	6.946456e-07
Marked as misclassified	No
Message-id	<1263895674.73.0.855261657965.issue7723@psf.upfronthosting.co.za>

Content
As far as I can see the docs for Python 3.x need to be adjusted. In particular http://docs.python.org/3.1/library/sqlite3.html#sqlite-and-python-types buffer should then there probably be replaced by memoryview. As far as I can see, the Python 3 definition of the old "buffer" interface is "anything that I can apply memoryview to". At least that was my interpretation when doing the Python 3 port of the sqlite3 module. Correct? When returning BLOBs, the sqlite3 module now returns bytes objects. I think this could be changed to memoryview without causing any problems.

Content

As far as I can see the docs for Python 3.x need to be adjusted. In particular http://docs.python.org/3.1/library/sqlite3.html#sqlite-and-python-types
buffer should then there probably be replaced by memoryview. As far as I can see, the Python 3 definition of the old "buffer" interface is "anything that I can apply memoryview to". At least that was my interpretation when doing the Python 3 port of the sqlite3 module.
Correct?
When returning BLOBs, the sqlite3 module now returns bytes objects. I think this could be changed to memoryview without causing any problems.

History
Date	User	Action	Args
2010年01月19日 10:07:55	ghaering	set	recipients: + ghaering, lemburg, pitrou, flox
2010年01月19日 10:07:54	ghaering	set	messageid: <1263895674.73.0.855261657965.issue7723@psf.upfronthosting.co.za>
2010年01月19日 10:07:53	ghaering	link	issue7723 messages
2010年01月19日 10:07:52	ghaering	create

homepage