cob*_*uli 4 python linux zeromq python-3.x pyzmq
到目前为止,这是我第一次使用 IPC,我编写了这个脚本:
#!/usr/bin/python
import zmq
context = zmq.Context()
socket = context.socket(zmq.PAIR)
socket.setsockopt(zmq.RCVTIMEO, 2000)
socket.connect ("ipc:///tmp/something")
socket.send(b"123")
try:
message = socket.recv()
except:
print("DEBUG!")
message = None
Run Code Online (Sandbox Code Playgroud)
当我的服务器脚本运行时(它只是发送一个答案),一切正常。
但是,当.recv()-call 超时(例如,因为没有服务器运行)时,脚本在“DEBUG!”打印后不会终止,我必须使用Ctrl+手动停止它C。
我尝试断开并关闭套接字,但它没有改变任何东西。
当我将整个脚本放入函数并调用它时,出现以下错误KeyboardInterrupt:
^CException ignored in: <bound method Context.__del__ of <zmq.sugar.context.Context object at 0x7f16a36d5128>>
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/zmq/sugar/context.py", line 46, in __del__
self.term()
File "zmq/backend/cython/context.pyx", line 136, in zmq.backend.cython.context.Context.term (zmq/backend/cython/context.c:2339)
File "zmq/backend/cython/checkrc.pxd", line 12, in zmq.backend.cython.checkrc._check_rc (zmq/backend/cython/context.c:3207)
KeyboardInterrupt
Run Code Online (Sandbox Code Playgroud)
我在 Arch Linux 上运行 Python 3.6.1 和 PyZMQ 模块版本 16.0.2。
该属性的默认值LINGER强制socket实例在尝试时等待.close()。因此,将其设置0为避免在实例化时出现此功能/行为,而不是最终挂在终止上。
import zmq
nIOthreads = 2 # ____POLICY: set 2+: { 0: non-blocking, 1: blocking, 2: ..., }
context = zmq.Context( nIOthreads ) # ____POLICY: set several IO-datapumps
socket = context.socket( zmq.PAIR )
socket.setsockopt( zmq.LINGER, 0 ) # ____POLICY: set upon instantiations
socket.setsockopt( zmq.AFFINITY, 1 ) # ____POLICY: map upon IO-type thread
socket.setsockopt( zmq.RCVTIMEO, 2000 )
socket.connect( "ipc:///tmp/something" )
socket.send( b"123" )
try:
message = socket.recv()
except:
print( "DEBUG!" )
message = None
finally:
socket.close() # ____POLICY: graceful termination
context.term() # ____POLICY: graceful termination
Run Code Online (Sandbox Code Playgroud)
| 归档时间: |
|
| 查看次数: |
4164 次 |
| 最近记录: |