Add Android support

[mhsmith]

See the linked issue for details:

• Android CI and binary releases cpython#137242

Since there will be no Android releases for Python 3.13 and earlier, the Android release job is skipped on those versions. See the "Temporarily point inputs ..." commit for a run that includes Android.

The lint and docs failures appear to be unrelated.

[freakboy3742]

Based on the current state of python/cpython#137186, this makes sense to me

[hugovk]

(Updated from main to fix mypy.)

[hugovk]

Let's set the defaults to a 3.14 commit, so we test Android for regular PRs and don't break it by mistake:

# Set from inputs for workflow_dispatch, or set defaults to test push/PR eventsenv:
GIT_REMOTE: ${{ github.event.inputs.git_remote || 'python' }}GIT_COMMIT: ${{ github.event.inputs.git_commit || '48f88310044c6ef877f3b0761cf7afece2f8fb3a' }}CPYTHON_RELEASE: ${{ github.event.inputs.cpython_release || '3.14.0rc1' }}

[mhsmith]

Let's set the defaults to a 3.14 commit, so we test Android for regular PRs and don't break it by mistake

I agree, but that'll have to wait until there's a tag that includes the Android build action from python/cpython#137186.

[mhsmith]

python/cpython#137186 has been changed to use an android.py ci command rather than a composite action, so I've updated this PR to match. Once again, I've tested an Android run by pointing it at my own repository (in the actions of the "Update type annotations" commit), and then reverted to the previous inputs.

[mhsmith]

I've updated run_release.py to include Android, and tested the relevant functions using my own SSH server. Because the Android binaries are now released via the same mechanism as the source tarballs, the temporary directory has been renamed from src to downloads.

I've also created python/peps#4541 to make the corresponding changes to PEP 101.

Pending the merge of python/cpython#137186, I think this PR is now complete.

[hugovk]

Thanks!

[hugovk]

(I guess technically they'll start in rc2 or rc3, but practically speaking I'm never going to do 3.14.0rc1 again :) And this much simplifies the logic.)

[hugovk]

@mhsmith The candidate of release candidate 2 is now building Android, in case you want to check it:

https://github.com/python/release-tools/actions/runs/16965004771

[mhsmith]

Looks good to me!

[TheDevilsNtheJenny]

I just started python and paid for the lifetime membership, but im only on the second course/step and im so lost i have no idea what im supposed to download or what im supposed to download it on, my phone? My chromebook ? Ugh please help

[webknjaz]

@TheDevilsNtheJenny you probably need to start at https://docs.python.org/3/tutorial/index.html and perhaps ask for help at https://discuss.python.org/c/help/7.
Whatever course you purchased, they will probably also be able to help you as this place has no affiliation with it.
This bug tracker, though, is not a good place for asking such questions. Bear in mind that disruptive activity may get you banned and you're expected to follow the CoC.
Cheers!