[Bug #1475554] Strengthen text to say 'must' instead of 'should'

This commit is contained in:
Andrew M. Kuchling 2006-06-03 18:33:35 +00:00
parent 29d530b3ef
commit 794c89b678
1 changed files with 2 additions and 2 deletions

View File

@ -548,7 +548,7 @@ are described in \ref{bltin-file-objects}, ``File Objects.'')
The file object references a \cfunction{dup()}ped version of the The file object references a \cfunction{dup()}ped version of the
socket file descriptor, so the file object and socket object may be socket file descriptor, so the file object and socket object may be
closed or garbage-collected independently. closed or garbage-collected independently.
The socket should be in blocking mode. The socket must be in blocking mode.
\index{I/O control!buffering}The optional \var{mode} \index{I/O control!buffering}The optional \var{mode}
and \var{bufsize} arguments are interpreted the same way as by the and \var{bufsize} arguments are interpreted the same way as by the
built-in \function{file()} function; see ``Built-in Functions'' built-in \function{file()} function; see ``Built-in Functions''
@ -647,7 +647,7 @@ Timeout mode internally sets the socket in non-blocking mode. The
blocking and timeout modes are shared between file descriptors and blocking and timeout modes are shared between file descriptors and
socket objects that refer to the same network endpoint. A consequence socket objects that refer to the same network endpoint. A consequence
of this is that file objects returned by the \method{makefile()} of this is that file objects returned by the \method{makefile()}
method should only be used when the socket is in blocking mode; in method must only be used when the socket is in blocking mode; in
timeout or non-blocking mode file operations that cannot be completed timeout or non-blocking mode file operations that cannot be completed
immediately will fail. immediately will fail.