-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-blocking behaviour (timeout = 0) is ignored #121
Comments
Same problem: eventlet/eventlet#616 @terryzhu suggested this workaround def setblocking(self, v):
+ if self._timeout == v:
+ return
if v:
self.settimeout(None)
else:
self.settimeout(0.0) I think, pysocks should use existing |
any fix for this? |
I no longer depend on PySocks, |
Hello! I'm facing a bit of an issue with PySocks and asyncio together (by using
loop.sock_connect
). As it turns out, PySocks seems to be ignoring the non-blocking behaviour. This seems to be the cause:PySocks/socks.py
Lines 94 to 110 in b687a34
Now, could I get some explanation on why that is needed? Here is the code to reproduce the issue:
The change that introduced this (a2cab50) does not give much information:
The text was updated successfully, but these errors were encountered: