-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
socket.getblocking() documentation lists opposite equivalence #104882
Labels
docs
Documentation in the Doc dir
Comments
AlexWaygood
pushed a commit
that referenced
this issue
Jun 4, 2023
…locking()` and `socket.gettimeout()` (#105026)
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 4, 2023
…t.getblocking()` and `socket.gettimeout()` (pythonGH-105026) (cherry picked from commit 5a5ed7a) Co-authored-by: Joe Geisbauer <joegeisbauer@gmail.com>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 4, 2023
…t.getblocking()` and `socket.gettimeout()` (pythonGH-105026) (cherry picked from commit 5a5ed7a) Co-authored-by: Joe Geisbauer <joegeisbauer@gmail.com>
Fixed, and backported to 3.12 and 3.11 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Documentation
The documentation for
socket.getblocking()
states:But that's the opposite of what it means. According to the source code,
getblocking()
returnsFalse
if and only ifgettimeout()
returns0.0.
Linked PRs
socket.getblocking()
andsocket.gettimeout()
#105026socket.getblocking()
andsocket.gettimeout()
(GH-105026) #105283socket.getblocking()
andsocket.gettimeout()
(GH-105026) #105284The text was updated successfully, but these errors were encountered: