[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Changes by Florent Xicluna : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Florent Xicluna added the comment: I propose to close this, since 2.7 is released and the situation is better in Python 3. -- resolution: -> wont fix status: open -> pending ___ Python tracker ___

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Benjamin Peterson added the comment: Documentation can always be updated later. -- nosy: +benjamin.peterson priority: release blocker -> normal ___ Python tracker ___ ___

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Gerhard Häring added the comment: I see that the status of this issue keeps changing. Now does anything in the sqlite3 module or the docs need to be changed? Or what's left to close this? -- ___ Python tracker __

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Changes by Benjamin Peterson : -- priority: deferred blocker -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Changes by Benjamin Peterson : -- priority: release blocker -> deferred blocker ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Florent Xicluna added the comment: So we keep buffer() as the standard way to create BLOBs for 2.x? It is the only use of "py3k deprecated" buffer() which cannot be replaced in 2.x. Set to "release blocker" until a decision is made. -- priority: critical -> release blocker _

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Antoine Pitrou added the comment: Pablo's documentation patch for py3k has been committed. -- ___ Python tracker ___ ___ Python-bugs-l

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Pablo Mouzo added the comment: I'm attaching a correction to sqlite3 documentation, removing all 'buffer' references and setting bytes as BLOB equivalent. -- keywords: +patch nosy: +pablomouzo Added file: http://bugs.python.org/file15977/issue7723-py3k-docs.diff __

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Antoine Pitrou added the comment: Hello Gerhard, > As far as I can see, the Python 3 definition of the old "buffer" > interface is "anything that I can apply memoryview to". Roughly, yes. > When returning BLOBs, the sqlite3 module now returns bytes objects. I > think this could be changed to

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Gerhard Häring added the comment: 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

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Marc-Andre Lemburg added the comment: Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > This is not exact. buffer() doesn't exist at all in 3.x, and it issues a > warning in 2.x when used with the -3 flag: > > $ ./python -3 > Python 2.7a2+ (trunk:77580M, Jan 17 2010, 16:51:51)

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Antoine Pitrou added the comment: This is not exact. buffer() doesn't exist at all in 3.x, and it issues a warning in 2.x when used with the -3 flag: $ ./python -3 Python 2.7a2+ (trunk:77580M, Jan 17 2010, 16:51:51) [GCC 4.4.1] on linux2 Type "help", "copyright", "credits" or "license" for mo

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Marc-Andre Lemburg added the comment: buffer() is only deprecated in Python 3.x, not in Python 2.7, so the current implementation is perfectly valid for Python 2.7. Note that buffer() has long been the preferred type for passing binary objects to and from a database. -- nosy: +lembur

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Florent Xicluna added the comment: Sidenotes: - documentation for Python 3 is outdated - it may be a release blocker, since there's no alternative: currently it uses exclusively buffer() for BLOB object -- ___ Python tracker

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Changes by Florent Xicluna : -- priority: high -> critical ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

Changes by Antoine Pitrou : -- assignee: -> ghaering nosy: +ghaering stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-lis

[issue7723] sqlite only accept buffer() for BLOB objects (input/output)

New submission from Florent Xicluna : Since buffer() is deprecated in Python 2.7, it should not be used for BLOB input/output. SAMPLES = ( ('unicode', u''), ('bytes', ''), ('buffer', buffer('')), # ('bytearray', bytearray('')), # unsupported # ('memoryview', memoryview(''))# unsu