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.

classification
Title: References to "pysqlite" in documentation of sqlite3 should be changed.
Type: Stage:
Components: Documentation Versions: Python 3.0, Python 3.1, Python 2.7, Python 2.6
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: MLModel, georg.brandl
Priority: normal Keywords:

Created on 2009-05-18 16:52 by MLModel, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg88037 - (view) Author: Mitchell Model (MLModel) Date: 2009-05-18 16:52
Why are there references to "pysqlite" in the documentation and examples
for the sqlite3 module. Was sqlite3 derived from the earlier pysqlite
module? Seems to me that all the references to "pysqlite" should read
"sqlite3", except maybe in a reworded attribution to the developer.
msg88043 - (view) Author: Mitchell Model (MLModel) Date: 2009-05-18 18:55
I see that the _sqlite .h and .c files, and the sqlite3/dbapi2.py file,
all use "pysqlite" instead of "sqlite3" internally. Should that be
changed too, or is there just no point? My main concern is that people
relatively new to Python who wouldn't be aware of the long history some
modules have and their migration from external packages into the
distribution (often with a name change) will be confused by mentions of
pysqlite in the documentation.
msg88128 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-05-20 18:31
pysqlite is an alias of sqlite3; it's developed outside of the core
under that name.  I agree that this can be confusing, and I've now
removed almost all mentions (and qualified the remaining one) in r72801.

I will not touch occurrences in source code; this will make syncing with
pysqlite unnecessarily hard.
History
Date User Action Args
2022-04-11 14:56:49adminsetgithub: 50305
2009-05-20 18:31:45georg.brandlsetstatus: open -> closed
resolution: fixed
messages: + msg88128
2009-05-18 18:55:09MLModelsetmessages: + msg88043
2009-05-18 16:52:25MLModelcreate