From 047e1c254f9ba007ed24284c94740cc34f7fb4d7 Mon Sep 17 00:00:00 2001 From: Dustin Ingram Date: Tue, 4 Feb 2025 15:57:07 +0000 Subject: [PATCH] Update PEP 738 to better specify platform tags --- peps/pep-0738.rst | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/peps/pep-0738.rst b/peps/pep-0738.rst index ede9aeeb1d6..b1fdd803ae9 100644 --- a/peps/pep-0738.rst +++ b/peps/pep-0738.rst @@ -358,6 +358,18 @@ the wheel was compiled. Installation tools such as pip should interpret this in a similar way to the existing macOS tags, i.e. an app with a minimum API level of N can incorporate wheels tagged with API level N or older. +* The lowest possible value for this component is ``"21"``; +* There is no upper bound. + +The ```` must be one of the supported architectures in `Architectures`_, +normalized to conform to :pep:`491` by replacing runs of non-alphanumeric +characters with an underscore. Thus there are four valid ```` components: + +* ``armeabi_v7a`` +* ``arm64_v8a`` +* ``x86`` +* ``x86_64`` + This format originates from the Chaquopy project, which currently maintains a `wheel repository `__ with tags varying between API levels 16 and 21. @@ -372,8 +384,8 @@ builds to their CI and release tooling. Adding Android support to tools like `crossenv `__ and `cibuildwheel `__ may be one way to achieve this. -The Android wheel tag format should also be added to the list of tags accepted -by PyPI. +The tag format for these Android platforms MUST be permitted as valid wheel +platform tags for a package index. PEP 11 Update