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
Using catkin_pip_package() with generate_message() actually breaks.
What happens (as of catkin_pip 0.2.2) is :
msg and srv are created in devel/lib/python2.7/dist-packages with an empty__init__.py
the ros1-pip-template.egg-link file is created in devel/lib/python2.7/site-packages
The link in the egg-link file seems to be checked after the path in PYTHONPATH (likely following default python handling of sys.path), and the package is found with an empty __init__.py, then it only contains msg and srv and not the code...
This is in practice not happening often, as people have taken the habit to split messages into a separate specific package (maybe for similar reasons ?). However we should support this properly, as catkin officially supports it.
The text was updated successfully, but these errors were encountered:
Note this might be mixed with the fact that a namespace package would make this work (message subpackage in one directory and module code in another_, but a usual python2 package would not...
Using
catkin_pip_package()
withgenerate_message()
actually breaks.What happens (as of catkin_pip 0.2.2) is :
msg
andsrv
are created indevel/lib/python2.7/dist-packages
with an empty__init__.py
devel/lib/python2.7/site-packages
The link in the
egg-link
file seems to be checked after the path in PYTHONPATH (likely following default python handling ofsys.path
), and the package is found with an empty__init__.py
, then it only containsmsg
andsrv
and not the code...This is in practice not happening often, as people have taken the habit to split messages into a separate specific package (maybe for similar reasons ?). However we should support this properly, as catkin officially supports it.
The text was updated successfully, but these errors were encountered: