mirror of
https://github.com/python/cpython.git
synced 2025-08-04 17:08:35 +00:00
gh-121905: Consistently use "floating-point" instead of "floating point" (GH-121907)
This commit is contained in:
parent
420d943128
commit
1a0c7b9ba4
100 changed files with 241 additions and 241 deletions
|
@ -412,7 +412,7 @@ since it is impossible to detect the termination of alien threads.
|
|||
timeout occurs.
|
||||
|
||||
When the *timeout* argument is present and not ``None``, it should be a
|
||||
floating point number specifying a timeout for the operation in seconds
|
||||
floating-point number specifying a timeout for the operation in seconds
|
||||
(or fractions thereof). As :meth:`~Thread.join` always returns ``None``,
|
||||
you must call :meth:`~Thread.is_alive` after :meth:`~Thread.join` to
|
||||
decide whether a timeout happened -- if the thread is still alive, the
|
||||
|
@ -794,7 +794,7 @@ item to the buffer only needs to wake up one consumer thread.
|
|||
occurs. Once awakened or timed out, it re-acquires the lock and returns.
|
||||
|
||||
When the *timeout* argument is present and not ``None``, it should be a
|
||||
floating point number specifying a timeout for the operation in seconds
|
||||
floating-point number specifying a timeout for the operation in seconds
|
||||
(or fractions thereof).
|
||||
|
||||
When the underlying lock is an :class:`RLock`, it is not released using
|
||||
|
@ -1021,7 +1021,7 @@ method. The :meth:`~Event.wait` method blocks until the flag is true.
|
|||
the the internal flag did not become true within the given wait time.
|
||||
|
||||
When the timeout argument is present and not ``None``, it should be a
|
||||
floating point number specifying a timeout for the operation in seconds,
|
||||
floating-point number specifying a timeout for the operation in seconds,
|
||||
or fractions thereof.
|
||||
|
||||
.. versionchanged:: 3.1
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue