First update: PYMAVLINK version conflicts.
One of the videos of the DroneKit section is dedicated to installing virtualenv to manage conflicting versions of pymavlink, as the version we were recommended to install does not play well with the recommended version of dronekit-sitl. Well, I’m glad to report I do not have that problem in my setup. Here are the versions of my dependencies:
$ pip3 freeze | grep -i mav
pip3 freeze | grep -i drone
As we can appreciate, they are all the latest versions as of today, no need for special versions. This is the output I get when I run the connection_template.py script without a connection string, which makes it start a default dronekit sitl:
$ python connection_template.py
Starting copter simulator (SITL)
Downloading SITL from http://dronekit-assets.s3.amazonaws.com/sitl/copter/sitl-linux-copter-3.3.tar.gz
Ready to boot.
CRITICAL:autopilot:APM:Copter V3.3 (d6053245)
CRITICAL:autopilot:barometer calibration complete
As far as I can tell, 0 problems!
I actually do encourage everyone to use virtualenvs as it is a clean way to keep your dependencies controlled, but I’m glad to report no special provisions are needed to make dronekit-sitl work with my setup.