Skip to content
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

Fix rosservice call for python3. #847

Merged
merged 1 commit into from
Jul 25, 2016
Merged

Fix rosservice call for python3. #847

merged 1 commit into from
Jul 25, 2016

Conversation

de-vri-es
Copy link
Contributor

rosservice was mistakenly passing a StringIO as buffer to rosgraph.network.read_ros_handshake_header even for python3. For python3 this needs to be a BytesIO object. This PR corrects that.

When running with python2, the old StringIO type is still used.

@wjwwood
Copy link
Member

wjwwood commented Jul 25, 2016

looks ok to me

@dirk-thomas
Copy link
Member

Thank you for the patch.

@dirk-thomas dirk-thomas merged commit 6af77dc into ros:kinetic-devel Jul 25, 2016
@de-vri-es
Copy link
Contributor Author

Thanks for the quick merge :)

rsinnet pushed a commit to MisoRobotics/ros_comm that referenced this pull request Jun 19, 2017
CBJamo added a commit to CBJamo/rqt_topic that referenced this pull request Nov 22, 2018
In python 3, message.serialize expects a buffer that will accept a
bytes-type input to it's write function. This commit uses the same
fix as ros_comm PR #847[1].

[1] ros/ros_comm#847
dirk-thomas pushed a commit to ros-visualization/rqt_topic that referenced this pull request Jan 9, 2020
In python 3, message.serialize expects a buffer that will accept a
bytes-type input to it's write function. This commit uses the same
fix as ros_comm PR #847[1].

[1] ros/ros_comm#847
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants