Kaydet (Commit) 321afa80 authored tarafından R. David Murray's avatar R. David Murray

Make punctuation prettier and break up run-on sentence.

üst 7e2801d1
...@@ -2107,7 +2107,7 @@ Beware replacing sys.stdin with a "file like object" ...@@ -2107,7 +2107,7 @@ Beware replacing sys.stdin with a "file like object"
os.close(sys.stdin.fileno()) os.close(sys.stdin.fileno())
In the :meth:`multiprocessing.Process._bootstrap` method of - this resulted in the :meth:`multiprocessing.Process._bootstrap` method --- this resulted
in issues with processes-in-processes. This has been changed to:: in issues with processes-in-processes. This has been changed to::
sys.stdin.close() sys.stdin.close()
...@@ -2116,7 +2116,7 @@ Beware replacing sys.stdin with a "file like object" ...@@ -2116,7 +2116,7 @@ Beware replacing sys.stdin with a "file like object"
Which solves the fundamental issue of processes colliding with each other Which solves the fundamental issue of processes colliding with each other
resulting in a bad file descriptor error, but introduces a potential danger resulting in a bad file descriptor error, but introduces a potential danger
to applications which replace :func:`sys.stdin` with a "file-like object" to applications which replace :func:`sys.stdin` with a "file-like object"
with output buffering, this danger is that if multiple processes call with output buffering. This danger is that if multiple processes call
:func:`close()` on this file-like object, it could result in the same :func:`close()` on this file-like object, it could result in the same
data being flushed to the object multiple times, resulting in corruption. data being flushed to the object multiple times, resulting in corruption.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment