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 |
terryzhu
added a commit
to terryzhu/eventlet
that referenced
this issue
Dec 24, 2020
terryzhu
added a commit
to terryzhu/eventlet
that referenced
this issue
Dec 24, 2020
|
any fix for this? |
|
I no longer depend on PySocks, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: