sqlite: delete some bsddb cargo-culted code to work around Python 2.3/2.4 bugs

diff --git a/Modules/_sqlite/module.c b/Modules/_sqlite/module.c
index 5f8aaf96b591c4fa6e8b9895120d1de0ce9d22e3..ffb711830bc616bd1efdf038d0828d1b1761627b 100644 (file)
--- a/Modules/_sqlite/module.c
+++ b/Modules/_sqlite/module.c
@@ -465,21 +465,6 @@ PyMODINIT_FUNC PyInit__sqlite3(void)
 
     pysqlite_BaseTypeAdapted = 0;
 
-    /* Original comment from _bsddb.c in the Python core. This is also still
-     * needed nowadays for Python 2.3/2.4.
-     *
-     * PyEval_InitThreads is called here due to a quirk in python 1.5
-     * - 2.2.1 (at least) according to Russell Williamson <merel@wt.net>:
-     * The global interpreter lock is not initialized until the first
-     * thread is created using thread.start_new_thread() or fork() is
-     * called.  that would cause the ALLOW_THREADS here to segfault due
-     * to a null pointer reference if no threads or child processes
-     * have been created.  This works around that and is a no-op if
-     * threads have already been initialized.
-     *  (see pybsddb-users mailing list post on 2002-08-07)
-     */
-    PyEval_InitThreads();
-
 error:
     if (PyErr_Occurred())
     {