Skip to content

Add support for Android #13299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
mhsmith opened this issue Mar 24, 2025 · 1 comment · May be fixed by #13303
Open
1 task done

Add support for Android #13299

mhsmith opened this issue Mar 24, 2025 · 1 comment · May be fixed by #13303
Labels
state: awaiting PR Feature discussed, PR is needed type: feature request Request for a new feature

Comments

@mhsmith
Copy link

mhsmith commented Mar 24, 2025

What's the problem this feature will solve?

Android has been an officially supported Python platform since Python 3.13. More recently, its wheel tag format was added to the PyPA specs page, and that format is now accepted by PyPI (e.g. see here).

pip should be able to install these wheels in two contexts:

  • Directly on an Android device, e.g. via the Termux app.
  • Through an app packaging tool such as Briefcase, using a command like pip install --platform android_21_arm64_v8a mypackage.

Describe the solution you'd like

To avoid repeating the confusion around adding iOS support (#13053), I think the best sequence would be:

Alternative Solutions

Briefcase and Chaquopy currently use a forked version of pip that's several years old. They therefore lack many of pip's recent features, such as the new resolver.

Termux and Kivy don't support Android wheels at all, and compile everything from source, which is much slower.

Code of Conduct

@mhsmith mhsmith added S: needs triage Issues/PRs that need to be triaged type: feature request Request for a new feature labels Mar 24, 2025
@ichard26 ichard26 added state: awaiting PR Feature discussed, PR is needed and removed S: needs triage Issues/PRs that need to be triaged labels Mar 26, 2025
@ichard26
Copy link
Member

Sounds good to me. Although this is already implied, it's worth stating that the pip core team will be entirely incapable of maintaining Android support. Thus, any bug-fixes or improvements will need to come from external contributors (like yourself, thank you!) who know the Android platform. This is also the case for iOS since no one on the core team uses pip on a smartphone.

Anyway, let's wait until packaging lands the Android support changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: awaiting PR Feature discussed, PR is needed type: feature request Request for a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants