[issue42624] sqlite3 package document mistake

Erlend Egeberg Aasland added the comment: *error handling => exception emitted -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue42624] sqlite3 package document mistake

Erlend Egeberg Aasland added the comment: ... and also bpo-16379 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue42624] sqlite3 package document mistake

Erlend Egeberg Aasland added the comment: Ref. bpo-24139 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue42624] sqlite3 package document mistake

Erlend Egeberg Aasland added the comment: Exception originates from _pysqlite_seterror() in Modules/_sqlite/util.c, line 64: https://github.com/python/cpython/blob/master/Modules/_sqlite/util.c#L64 Error code 1 (SQLITE_ERROR, https://sqlite.org/rescode.html#error) is a generic sqlite3 error.

[issue42624] sqlite3 package document mistake

LIU Qingyuan added the comment: Python 3.9.1 (default, Dec 11 2020, 14:32:07) [GCC 7.3.0] :: Anaconda, Inc. on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sqlite3 >>> conn = sqlite3.connect("test.db") >>> conn.execute("CREATE TABLE test (id INTEGER,

[issue42624] sqlite3 package document mistake

Change by Erlend Egeberg Aasland : -- nosy: +erlendaasland ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue42624] sqlite3 package document mistake

Terry J. Reedy added the comment: The doc is the same in 3.10. What OS and exact Python release? Can you post minimal code that verifies your claim? (Someone what have to verify with 3.10 also.) This would strike me as an error in the code. We can fix 'wrong Exception' in the next release

[issue42624] sqlite3 package document mistake

Change by Karthikeyan Singaravelan : -- nosy: +berker.peksag, ghaering ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue42624] sqlite3 package document mistake

New submission from LIU Qingyuan : In the document about sqlite3 package, it was suggested that when users are trying to create a table already exists, sqlite3.ProgrammingError is going to be thrown. However, the actual exception thrown is sqlite3.OperationalError, which is inconsistent with