diff options
| author | Tim Peters <tim.peters@gmail.com> | 2004-10-11 02:40:51 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2004-10-11 02:40:51 (GMT) |
| commit | 7f468f29f49786988e4f1a005174578fc83c7eb9 (patch) | |
| tree | 0a675ca5df1a5df96404213998dc51672394328e /Misc | |
| parent | 89c0ec9beba4e6b086e74345bc1ef15041bd5e7d (diff) | |
| download | cpython-7f468f29f49786988e4f1a005174578fc83c7eb9.zip cpython-7f468f29f49786988e4f1a005174578fc83c7eb9.tar.gz cpython-7f468f29f49786988e4f1a005174578fc83c7eb9.tar.bz2 | |
SF patch 1044089: New C API function PyEval_ThreadsInitialized(), by Nick
Coghlan, for determining whether PyEval_InitThreads() has been called.
Also purged the undocumented+unused _PyThread_Started int.
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/NEWS | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -136,6 +136,11 @@ Build C API ----- +- SF patch 1044089: New function ``PyEval_ThreadsInitialized()`` returns + non-zero if PyEval_InitThreads() has been called. + +- The undocumented and unused extern int ``_PyThread_Started`` was removed. + - The C API calls ``PyInterpreterState_New()`` and ``PyThreadState_New()`` are two of the very few advertised as being safe to call without holding the GIL. However, this wasn't true in a debug build, as bug 1041645 |