Search Criteria
Package Details: python-pymavlink-git r3217.fcaa2c7d-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/python-pymavlink-git.git (read-only, click to copy) |
|---|---|
| Package Base: | python-pymavlink-git |
| Description: | python MAVLink interface and utilities |
| Upstream URL: | https://github.com/ArduPilot/pymavlink/ |
| Licenses: | LGPL v3 |
| Conflicts: | python-pymavlink, python2-pymavlink, python2-pymavlink-git |
| Provides: | python-pymavlink |
| Submitter: | bobpaul |
| Maintainer: | bobpaul |
| Last Packager: | bobpaul |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2019-09-11 19:00 (UTC) |
| Last Updated: | 2025-08-01 18:31 (UTC) |
Dependencies (3)
- python-lxml
- cython (cython-gitAUR) (make)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
Required by (1)
- mavproxy-git (requires python-pymavlink)
Latest Comments
insmtr commented on 2025-07-07 06:52 (UTC)
In the latest version of pymavlink, the developers have removed the reference to python-future, so you no longer need to use the patch. Seen in https://github.com/ArduPilot/pymavlink/commit/a5844d30e75e2f96dd7abb4e28bd9cf02f1451d2
bobpaul commented on 2025-01-13 23:27 (UTC)
@dreieck I pushed an update which removes the need for future. It was only used in a couple of spots and removal looked pretty safe. It's not thoroughly tested.
bobpaul commented on 2025-01-13 19:02 (UTC)
@dreieck That's a request for upstream. The pymavlink project still officially support Python2 as well as Python3. They do have an issue open from several years ago to drop Python2 support and I don't think they've made a final decision about when they intend to do that.
dreieck commented on 2025-01-11 15:57 (UTC)
If possible, please remove the dependency on
python-furure/ make the package working withoutpython-future:Regards and thanks for this package!
acxz commented on 2020-03-20 05:30 (UTC) (edited on 2020-03-20 05:33 (UTC) by acxz)
@bobpaul thx for the fast response! I am getting the following issue when installing
mavlinkfrom the AUR. (I just recently created it.)https://github.com/acxz/pkgbuilds/issues/19
It could be the release of
mavlinkis so old that it assumesmavgenis in tools. Let me try withmavlink-git.EDIT: Yeah
mavlink-gitworked just fine for me, sorry to bother you!bobpaul commented on 2020-03-20 04:23 (UTC)
Are you sure that's the correct module path? The standalone mavgen.py script gets mavgen from generator, not tools:
acxz commented on 2020-03-19 23:48 (UTC)
While this package does build for me, it seems like it is not installing the `pymavlink.tools.mavgen' module. Can you take a look into this?