Closed gavanderhoorn closed 5 years ago
Any haros
verb and haros
itself actually fail with ImportError: No module named rosgraph.names
.
Yes, there are a few assumptions that are not really well documented, as I have not had enough users yet to realise these oversights. One of them is the source
ing of setup.bash
.
I would like a more in depth fix for the README, possibly splitting it into multiple files, and document each of them a little bit better. In the meantime, I should take your suggestion of changing the order of those statements, so that things are less confusing.
The import error on all verbs is also expected, since I am not doing conditional imports (although I have been thinking about this as a way to solve a few issues, and possibly reduce dependencies).
Both #43 and #44 should temporarily solve this, right? Minus the overall improvements on the README.
I've commented on #43 and #44.
The README was updated with a note on the requirements of setup.bash
, see https://github.com/git-afsantos/haros/commit/ab05399e7622fb7adfe024e92cab46067d8c7c44
I think I have minimally addressed all points in this issue, until I get to work on a proper rehaul of the documentation, so I will be closing this. Reopen if you feel something should be better addressed.
Connected to #38.
$me
being a stupid user again.After a
pip install haros
, invokingharos init
results in:Running
source /opt/ros/kinetic/setup.bash
fixes that.Another invocation then fails with:
I realise the ROS dependency is documented (implicitly) with:
Not every ROS user will have their shell automatically
source /opt/ros/kinetic/setup.bash
though, so perhaps that should be added to the readme.Also: I realise the
pyflwor
dependency is actually documented in the Requirements section, but the command that installs it -- and the other dependencies -- don't appear in the readme until after we've been told to runharos init
.Perhaps the order of these parts of the readme should be reversed?