| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Suppose I have a package with two sub directories "src" and "test". Suppose I have a module "a.py" in "src". How do I in a script in "test" import from "a.py"? What is the correct method with regard to finding "a.py" when executing?
The recommended method is to use the nosetests library to write tests fpr python. The command is nose. Nose automatically sets the PYTHONPATH before running the tests when you use reasonable names for your folders, like src and test. Doing so, in a python file in the test folder you can simply write "import foo.bar" to import a module defined in src/foo/bar.py.
When you write python modules with catkin, you should also use a setup.py file and the catkin_python_setup macro in your CMakeLists.txt file. More information can be found in the catkin documentation, and rospy tutorials, such as here: http://ros.org/wiki/rospy_tutorials/Tutorials/Makefile and here: http://ros.org/rosdoclite/groovy/api/catkin/html/user_guide/setup_dot_py.html
setup.py is the standard build file for python projects. In our case, you declare the scripts and packages from your project, and setup.py makes sure those get installed to the right locations. More info here: http://ros.org/rosdoclite/groovy/api/catkin/html/user_guide/setup_dot_py.html
So are you saying that the thing in "packages" in setup.py is not ros packages at all? Are they Python packages or what are they? And if they are ROS packages what is a "relay package" talked about on the web page you gave? (Re-reading this now after reading the SIG discussion about setup.py).
what happens if you accidentally run the setup.py file the tutorial said it can break your ROS installation? Does this mean you have to reinstall ROS if you do this? Is it possible to keep a back up of your ROS workspace and just replace it?
Asked: 2013-01-16 11:44:46 -0500
Seen: 1,085 times
Last updated: Jan 18 '13
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
