Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Consequence of setup.py

asked 2018-06-25 01:57:53 -0500

JayDe
85 ●12 ●15 ●19

Hi,

I am currently setting up my first python based node. I have included a setup.py into my project and added the "catkin_python_setup()" macro in my CMakeLists.txt. I am now wondering, what the consequence of this is. Or, said differently, where can I see the result of adding setup.py and the macro?

I have checked the $PYTHONPATH and found that my python package can be found in /path_to_workspace/devel/lib/python2.7/dist-packages/mypackage. Am I right that this folder has been generated by catkin when running setup.py? Are the modules of my package mypackage made available through /path_to_workspace/devel/lib/python2.7/dist-packages/mypackage/__init__.py?

Thank you!

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2018-06-25 10:15:30 -0500

pgorczak
446 ●4 ●5 ●11

Correct! As long as you're using the devel space, catkin generates the file you mentioned via a cmake macro. When it is imported at runtime, it adds your source files (src/...) to the Python module path. As a consequence, you don't have to re-build your workspace unless you change setup.py itself.

edit flag offensive delete link

add a comment

Question Tools

2 followers

Stats

Asked: 2018-06-25 01:57:53 -0500

Seen: 122 times

Last updated: Jun 25 '18

Consequence of setup.py edit

1 Answer

Question Tools

Stats

Related questions

Consequence of setup.py