1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Benjamin Peterson 2017-09-22 23:25:28 -07:00 committed by GitHub
parent 058de11360
commit c8a6e5b18d
1 changed files with 0 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Modules/_sqlite/module.c
View File

@ -465,21 +465,6 @@ PyMODINIT_FUNC PyInit__sqlite3(void)
pysqlite_BaseTypeAdapted = 0; 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: error:
if (PyErr_Occurred()) if (PyErr_Occurred())
{ {