PEP 475: fix typos
This commit is contained in:
parent
e8bcf5c21a
commit
09d36fba17
|
@ -135,7 +135,7 @@ on some signals:
|
|||
``SIGINT``
|
||||
* Use a I/O multiplexing function like ``select()`` with the Python
|
||||
signal "wakeup" file descriptor: see the function
|
||||
``signal.set_wakeupfd()``.
|
||||
``signal.set_wakeup_fd()``.
|
||||
|
||||
|
||||
Proposition
|
||||
|
@ -184,14 +184,14 @@ If such applications exist, they are not portable and are subject to
|
|||
race conditions (deadlock if the signal comes before the system call).
|
||||
These applications must be fixed to handle signals differently, to
|
||||
have a reliable behaviour on all platforms and all Python versions.
|
||||
For example, use a signal handle which raises an exception, or use a
|
||||
For example, use a signal handler which raises an exception, or use a
|
||||
wakeup file descriptor.
|
||||
|
||||
For applications using event loops, ``signal.set_wakeup_fd()`` is the
|
||||
recommanded option to handle signals. The signal handler writes signal
|
||||
numbers into the file descriptor and the event loop is awaken to read
|
||||
them. The event loop can decide how to handle these signals without
|
||||
the restriction of signal handlers.
|
||||
them. The event loop can handle these signals without the restriction
|
||||
of signal handlers.
|
||||
|
||||
|
||||
Appendix
|
||||
|
|
Loading…
Reference in New Issue