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
When working on a python package, I usually do not assume anything in the environment.
Software is after all generic and abstract, and the environment should, ideally, not matter.
Afterall a python script can easily check and adapt the environment, so that it can do its job.
Basically replacing the "source .../setup.bash" call by a python function call, so that ROS can be easily "activated / deactivated" from python code.
It s currently very basic, and there is probably a better/simpler way of doing it ( like calling the _setup_util.py from the workspaces we want to use pyros-dev/pyros-setup#10).
It would be useful to have somewhere...
The text was updated successfully, but these errors were encountered:
That looks potentially interesting. How about submitting a PR to add documentation for (or at least a pointer to) it to the top-level README.md in this repo?
When working on a python package, I usually do not assume anything in the environment.
Software is after all generic and abstract, and the environment should, ideally, not matter.
Afterall a python script can easily check and adapt the environment, so that it can do its job.
I m currently working on a package that dynamically setup ROS environment : https://github.com/asmodehn/pyros-setup.
Basically replacing the "source .../setup.bash" call by a python function call, so that ROS can be easily "activated / deactivated" from python code.
It s currently very basic, and there is probably a better/simpler way of doing it ( like calling the _setup_util.py from the workspaces we want to use pyros-dev/pyros-setup#10).
It would be useful to have somewhere...
The text was updated successfully, but these errors were encountered: