ArduPilot / ArduPilot/pymavlink

Please straighten out your supported Python versions and dependencies

Open
#976 10 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
728
Forks
739
Avg merge
4d 10h
Merged PRs (30d)
7

Description

I just came back to this after several years and there seems to be *zero progress* in terms of cleaning up Python version support or packaging. Meaning `setup.py` *still requires future pkg* even though several other places claim only py36 or later (and several variants thereof). This is getting ridiculous trying to maintain a package that won't let go of out-dated dependencies. The world moves on and even bionic has been declared lifeless. Please lurch forward into at least the early 21st century...

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by auditing setup.py and the other Python-version and dependency declarations mentioned in the issue, especially the requirement for future. Define one consistent supported-version policy, remove outdated dependency constraints, and verify that the package metadata agrees across the project. Done means the supported Python versions and packaging dependencies are consistent and installable.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.