installing local python packages into virtualenv about catkin_virtualenv

[paulbovbel]

so, foo is a catkin package correct? The reason it's visible is that when you source setup.bash, your ROS workspace gets tacked onto your PYTHONPATH, and all your ROS python packages become available. However nothing activates the virtualenv for you, meaning bar isn't visible.

---

I have a feeling I haven't explained the intent of this library properly in the README. What this library does, is create a virtualenv for package foo, that gets activated automatically whenever you rosrun any scripts or run tests (catkin_add_nosetets) from package foo. You shouldn't have to activate the virtualenv manually, unless you're trying to do something unexpected.

[paulbovbel]

Closing due to inactivity

[Achllle]

What this library does, is create a virtualenv for package foo, that gets activated automatically whenever you rosrun any scripts or run tests (catkin_add_nosetets) from package foo. You shouldn't have to activate the virtualenv manually, unless you're trying to do something unexpected.

This would be a great addition to the readme imo. I was trying to use this somehow in parallel with catkin_python_setup which would allow me to release a package with bloom that you can import.