We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With commit b509515 (checked both on Hydro and Groovy on both Raring and Precise):
Hydro
Groovy
Raring
Precise
$ ipython -i `rospack find nextage_ros_bridge`/script/nextage.py RobotHardware0 /opt/jsk/etc/HIRONX/model/main.wrl -- -ORBInitRef NameService=corbaloc:iiop:192.168.128.10:15005/NameService Python 2.7.4 (default, Sep 26 2013, 03:20:26) Type "copyright", "credits" or "license" for more information. IPython 0.13.2 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details. --------------------------------------------------------------------------- ImportError Traceback (most recent call last) /usr/lib/python2.7/dist-packages/IPython/utils/py3compat.pyc in execfile(fname, *where) 176 else: 177 filename = fname --> 178 __builtin__.execfile(filename, *where) /home/n130s/data/Dropbox/ROS/hydro_raring/catkinws/src/tork-a/rtmros_nextage/nextage_ros_bridge/script/nextage.py in <module>() 37 38 import argparse ---> 39 import rtm 40 41 from nextage_ros_bridge import nextage_client ImportError: No module named rtm
Btw this is likely to occur with hironx too because of this commit.
hironx
Any workaround @emijah @k-okada ?
The text was updated successfully, but these errors were encountered:
(nextage_ros_bridge/nextage.py) Fix to #24
49d636a
Fixed via 49d636a
Sorry, something went wrong.
No branches or pull requests
With commit b509515 (checked both on
Hydro
andGroovy
on bothRaring
andPrecise
):Btw this is likely to occur with
hironx
too because of this commit.Any workaround @emijah @k-okada ?
The text was updated successfully, but these errors were encountered: