Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 4c1f5ec

Browse files
committed
Trim trailing whitespace.
1 parent dcb9d94 commit 4c1f5ec

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

Python/pystate.c

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -271,7 +271,7 @@ PyThreadState_Swap(PyThreadState *new)
271271

272272
_PyThreadState_Current = new;
273273
/* It should not be possible for more than one thread state
274-
to be used for a thread. Check this the best we can in debug
274+
to be used for a thread. Check this the best we can in debug
275275
builds.
276276
*/
277277
#if defined(Py_DEBUG) && defined(WITH_THREAD)
@@ -385,8 +385,8 @@ PyThreadState_IsCurrent(PyThreadState *tstate)
385385
static PyInterpreterState *autoInterpreterState = NULL;
386386
static int autoTLSkey = 0;
387387

388-
/* Internal initialization/finalization functions called by
389-
Py_Initialize/Py_Finalize
388+
/* Internal initialization/finalization functions called by
389+
Py_Initialize/Py_Finalize
390390
*/
391391
void _PyGILState_Init(PyInterpreterState *i, PyThreadState *t)
392392
{
@@ -418,8 +418,8 @@ PyGILState_STATE PyGILState_Ensure(void)
418418
{
419419
int current;
420420
PyThreadState *tcur;
421-
/* Note that we do not auto-init Python here - apart from
422-
potential races with 2 threads auto-initializing, pep-311
421+
/* Note that we do not auto-init Python here - apart from
422+
potential races with 2 threads auto-initializing, pep-311
423423
spells out other issues. Embedders are expected to have
424424
called Py_Initialize() and usually PyEval_InitThreads().
425425
*/
@@ -438,7 +438,7 @@ PyGILState_STATE PyGILState_Ensure(void)
438438
PyEval_RestoreThread(tcur);
439439
/* Update our counter in the thread-state - no need for locks:
440440
- tcur will remain valid as we hold the GIL.
441-
- the counter is safe as we are the only thread "allowed"
441+
- the counter is safe as we are the only thread "allowed"
442442
to modify this value
443443
*/
444444
tcur->gilstate_counter++;
@@ -453,7 +453,7 @@ void PyGILState_Release(PyGILState_STATE oldstate)
453453
"but no thread-state for this thread");
454454
/* We must hold the GIL and have our thread state current */
455455
/* XXX - remove the check - the assert should be fine,
456-
but while this is very new (April 2003), the extra check
456+
but while this is very new (April 2003), the extra check
457457
by release-only users can't hurt.
458458
*/
459459
if (!PyThreadState_IsCurrent(tcur))
@@ -462,7 +462,7 @@ void PyGILState_Release(PyGILState_STATE oldstate)
462462
tcur->gilstate_counter -= 1;
463463
assert (tcur->gilstate_counter >= 0); /* illegal counter value */
464464

465-
/* If we are about to destroy this thread-state, we must
465+
/* If we are about to destroy this thread-state, we must
466466
clear it while the lock is held, as destructors may run
467467
*/
468468
if (tcur->gilstate_counter==0) {

0 commit comments

Comments
 (0)