Closed
Description
python-for-android currently requires obsolete versions of the pep517 Python package at setuptools-based installation time via a pep517<0.7.0 requirement in the top-level setup.py script. This is bad for any number of obvious reasons, including:
pep517 0.6.0, the most recent version of this package to satisfy this constraint, is nearly three years old. In Python years,pep517is the geriatric centenarian with insufferable incontinence that habitually screeches "Gituffmuhlaaaaawn!" while throwing mouldy wonder bread at passing codebases.pep517 0.6.0is so old that it's only tested to work under Python 3.4–3.7. Of those, only Python 3.7 has yet to hit its official End-of-Life (EOL) – but even that will happen shortly.pep517 0.6.0is no longer packaged by any system package managers (e.g., Debian'sapt, Arch'spacman, Gentoo'semerge). It's unclear whetherpep517 0.6.0even can be packaged by any system package managers or run under actively developed Python versions. By transitivity,python-for-androiditself can no longer be reasonably packaged for any Linux distros.
In short, the pep517<0.7.0 constraint needs to be relaxed to cover the most recent stable release of pep517. In theory, this should be trivial; the p4a codebase only internally imports from pep517 twice in the python-for-android.pythonpackage submodule.
Thanks as always for all the phenomenal volunteerism, p4a team! You make the impossible at least slightly possible. 🤠
Metadata
Metadata
Assignees
Labels
No labels