You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/birkenfeld'closed_at=<Date2009-05-20.18:31:45.525>created_at=<Date2009-05-18.16:52:25.732>labels= ['docs']
title='References to "pysqlite" in documentation of sqlite3 should be changed.'updated_at=<Date2009-05-20.18:31:45.502>user='https://github.com/MLModel'
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.
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.
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.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: