You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a Python 3.8.5 venv and rospy installed from rospypi, termination of scripts can result in the following traceback:
Traceback (most recent call last):
File "C:\Python38\lib\threading.py", line 932, in _bootstrap_innerself.run()
File "C:\Python38\lib\threading.py", line 870, in runself._target(*self._args, **self._kwargs)
File "C:\...\venv_rospypi\lib\site-packages\rospy\impl\tcpros_base.py", line 160, in run
(e_errno, msg) = e.args
ValueError: too many values to unpack (expected 2)
On that system, e.args is actually a 3-tuple: errno, function, msg. Upstream rospy seems to handle that (from here):
exceptIOErrorase:
(e_errno, msg, *_) =e.args
(although I don't believe msg will actually contain the message in that case)
With a Python 3.8.5 venv and
rospy
installed fromrospypi
, termination of scripts can result in the following traceback:On that system,
e.args
is actually a 3-tuple:errno, function, msg
. Upstreamrospy
seems to handle that (from here):(although I don't believe
msg
will actually contain the message in that case)This was fixed in ros/ros_comm#2050 in
rospy
.Is that not included in the
rospy
distributed byrospypi
?The text was updated successfully, but these errors were encountered: