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

Sat Sep 23 02:25:31 EDT 2017

https://github.com/python/cpython/commit/c8a6e5b18d3c3df04c17ed7761e34487971c82ff
commit: c8a6e5b18d3c3df04c17ed7761e34487971c82ff
branch: master
author: Benjamin Peterson <benjamin at python.org>
committer: GitHub <noreply at github.com>
date: 2017年09月22日T23:25:28-07:00
summary:
sqlite: delete some bsddb cargo-culted code to work around Python 2.3/2.4 bugs
files:
M Modules/_sqlite/module.c

diff --git a/Modules/_sqlite/module.c b/Modules/_sqlite/module.c
index 5f8aaf96b59..ffb711830bc 100644
--- 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 at 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())
 {
