Removed obsolete references to pysqlite.

Obsolete since 1b06d5e6f6be8e567ce78c892c485af039830d7d.

django/db/backends/sqlite3/base.py

@@ -158,7 +158,7 @@ class DatabaseWrapper(BaseDatabaseWrapper):
         # between multiple threads. The safe-guarding will be handled at a
         # higher level by the `BaseDatabaseWrapper.allow_thread_sharing`
         # property. This is necessary as the shareability is disabled by
-        # default in pysqlite and it cannot be changed once a connection is
+        # default in sqlite3 and it cannot be changed once a connection is
         # opened.
         if "check_same_thread" in kwargs and kwargs["check_same_thread"]:
             warnings.warn(
@@ -357,7 +357,7 @@ FORMAT_QMARK_REGEX = _lazy_re_compile(r"(?<!%)%s")
 
 class SQLiteCursorWrapper(Database.Cursor):
     """
-    Django uses "format" style placeholders, but pysqlite2 uses "qmark" style.
+    Django uses "format" style placeholders, but sqlite3 uses "qmark" style.
     This fixes it -- but note that if you want to use a literal "%s" in a query,
     you'll need to use "%%s".
     """

django/db/backends/sqlite3/operations.py

@@ -168,9 +168,7 @@ class DatabaseOperations(BaseDatabaseOperations):
 
     def last_executed_query(self, cursor, sql, params):
         # Python substitutes parameters in Modules/_sqlite/cursor.c with:
-        # pysqlite_statement_bind_parameters(
-        #   self->statement, parameters, allow_8bit_chars
-        # );
+        # bind_parameters(state, self->statement, parameters);
         # Unfortunately there is no way to reach self->statement from Python,
         # so we quote and substitute parameters manually.
         if params:

docs/releases/1.4.txt

@@ -900,8 +900,8 @@ object, use ``django.db.connections[DEFAULT_DB_ALIAS]`` instead.
 
 As part of this change, all underlying SQLite connections are now enabled for
 potential thread-sharing (by passing the ``check_same_thread=False`` attribute
-to pysqlite). ``DatabaseWrapper`` however preserves the previous behavior by
-disabling thread-sharing by default, so this does not affect any existing
+to ``pysqlite``). ``DatabaseWrapper`` however preserves the previous behavior
+by disabling thread-sharing by default, so this does not affect any existing
 code that purely relies on the ORM or on ``DatabaseWrapper.cursor()``.
 
 Finally, while it's now possible to pass connections between threads, Django

docs/spelling_wordlist

@@ -387,7 +387,6 @@ psycopg
 Punycode
 Puthraya
 pyformat
-pysqlite
 pythonic
 qs
 queryset