Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 14 additions & 2 deletions peps/pep-0738.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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 ``<abi>`` 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 ``<abi>`` components:

* ``armeabi_v7a``
* ``arm64_v8a``
* ``x86``
* ``x86_64``

This format originates from the Chaquopy project, which currently maintains a
`wheel repository <https://chaquo.com/pypi-13.1/>`__ with tags varying between
API levels 16 and 21.
Expand All @@ -372,8 +384,8 @@ builds to their CI and release tooling. Adding Android support to tools like
`crossenv <https://crossenv.readthedocs.io/>`__ and `cibuildwheel
<https://cibuildwheel.readthedocs.io/>`__ 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
Expand Down