mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-08-04 08:59:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

gh-121905: Consistently use "floating-point" instead of "floating point" (GH-121907)

Browse source
This commit is contained in:
Serhiy Storchaka 2024-07-19 11:06:02 +03:00 • committed by GitHub
parent 420d943128
commit 1a0c7b9ba4
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
100 changed files with 241 additions and 241 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Lib/threading.py
View file

@ -336,7 +336,7 @@ class Condition:
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 RLock, it is not released using its
@ -646,7 +646,7 @@ class Event:
the optional 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).
This method returns the internal flag on exit, so it will always return
@ -1059,7 +1059,7 @@ class Thread:
or until the optional 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 join() always returns None, you must call
is_alive() after join() to decide whether a timeout happened -- if the
thread is still alive, the join() call timed out.