diff options
| author | Benjamin Peterson <benjamin@python.org> | 2017-09-23 06:25:28 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-23 06:25:28 (GMT) |
| commit | c8a6e5b18d3c3df04c17ed7761e34487971c82ff (patch) | |
| tree | fcaeaa99736a1498e3530ce03ea434e8806fe731 /Modules/_sqlite | |
| parent | 058de11360ea6816a6e978c7be0bcbea99a3f7da (diff) | |
| download | cpython-c8a6e5b18d3c3df04c17ed7761e34487971c82ff.zip cpython-c8a6e5b18d3c3df04c17ed7761e34487971c82ff.tar.gz cpython-c8a6e5b18d3c3df04c17ed7761e34487971c82ff.tar.bz2 | |
sqlite: delete some bsddb cargo-culted code to work around Python 2.3/2.4 bugs
Diffstat (limited to 'Modules/_sqlite')
| -rw-r--r-- | Modules/_sqlite/module.c | 15 |
1 files changed, 0 insertions, 15 deletions
diff --git a/Modules/_sqlite/module.c b/Modules/_sqlite/module.c index 5f8aaf9..ffb7118 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@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()) { |