Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

avoiding having to call catkin_make for changes to python modules?

While coding in Python (and using rosbuild) I find it very convenient to not to have to 'make' before testing my code:

e.g. I change a module that my Python script uses and without any 'make' I can run my script again and have it use the updated module.

With catkin, am I correct in understanding that I will need to do a catkin_make each time so that the updated module gets copied into the devel space and is thus available to my script?

avoiding having to call catkin_make for changes to python modules?

While coding in Python (and using rosbuild) I find it very convenient to not to have to 'make' before testing my code:

e.g. I change a module (which lives in its own ROS package) that my Python script uses and without any 'make' I can kill the script, run my script it again and have it use the updated module.

With catkin, am I correct in understanding that I will need to do a catkin_make each time so that the updated module gets copied into the devel space and is thus available to my script?

avoiding having to call catkin_make for changes to python modules?

While coding in Python (and using rosbuild) I find it very convenient to not to have to 'make' before testing my code:

e.g. I change a module (which lives in its own ROS package) that my Python script uses and without any 'make' I kill the script, run it again and have it use the updated module.

With catkin, am I correct in understanding that I will need to do a catkin_make each time so that the updated module gets copied into the devel space and is thus available to my script?

avoiding having to call catkin_make for changes to python modules?

While coding in Python (and using rosbuild) I find it very convenient to not to have to 'make' before testing my code:

e.g. I change a module (which lives in its own ROS package) that my Python script uses and without any 'make' I kill the script, run it again and have it use the updated module.

With catkin, am I correct in understanding that I will need to do a catkin_make each time so that the updated module gets copied into the devel space and is thus available to my script?