From: Tim Peters <tim.peters@gmail.com>
Date: Fri, 1 Sep 2000 19:26:36 +0000 (+0000)
Subject: Repaired damaged comments, and extra spaces in fatal error msgs we'd better
X-Git-Tag: v2.0b1~77
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=9acdd3aed84949286995f8e3df26b41ec8065228;p=python

Repaired damaged comments, and extra spaces in fatal error msgs we'd better
not ever see!
---

diff --git a/Modules/posixmodule.c b/Modules/posixmodule.c
index 42bde9758a..d921eee5a5 100644
--- a/Modules/posixmodule.c
+++ b/Modules/posixmodule.c
@@ -2726,13 +2726,13 @@ static int _PyPclose(FILE *file)
 		 * an exception.  Just die.
 		 */
 		 Py_FatalError("unable to allocate interpreter state "
-		 	       " when closing popen object.");
+		 	       "when closing popen object.");
 		 return -1;  /* unreachable */
 	}
 	pThreadState = PyThreadState_New(pInterpreterState);
 	if (!pThreadState) {
 		 Py_FatalError("unable to allocate thread state "
-		 	       " when closing popen object.");
+		 	       "when closing popen object.");
 		 return -1;  /* unreachable */
 	}
 	/* Grab the global lock.  Note that this will deadlock if the
@@ -2802,9 +2802,9 @@ static int _PyPclose(FILE *file)
 #ifdef WITH_THREAD
 	/* Tear down the thread & interpreter states.
 	 * Note that interpreter state clear & delete functions automatically
-	 * call the thread & clear functions, and * indeed insist on doing
-	 * that themselves.  The lock must be held during the clear, but need
-	 * not be held during the delete.
+	 * call the thread clear & delete functions, and indeed insist on
+	 * doing that themselves.  The lock must be held during the clear, but
+	 * need not be held during the delete.
 	 */
 	PyInterpreterState_Clear(pInterpreterState);
 	PyEval_ReleaseThread(pThreadState);
@@ -2813,7 +2813,8 @@ static int _PyPclose(FILE *file)
 
 	return result;
 }
-#else
+
+#else /* which OS? */
 static PyObject *
 posix_popen(PyObject *self, PyObject *args)
 {