Skip to content
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

PEP 738: Better specify platform tags #4250

Closed
wants to merge 1 commit into from
Closed

Conversation

di
Copy link
Member

@di di commented Feb 4, 2025

Found this when working on pypi/warehouse#17549:

  • Better specify the upper/lower bounds for the API version;
  • Explain that the architectures must be normalized to be included in valid wheel tags;
  • Strengthen the requirement that package indices must add support;

cc @mhsmith @encukou.


📚 Documentation preview 📚: https://pep-previews--4250.org.readthedocs.build/

@di di requested a review from encukou as a code owner February 4, 2025 16:29
@AA-Turner AA-Turner changed the title Update PEP 738 to better specify platform tags PEP 738: Better specify platform tags Feb 4, 2025
@AA-Turner
Copy link
Member

Generally we tend not to make substantive changes to Final PEPs, though it may be that there's nowhere better to record this information. There's no information on packaging tags here, and packaging.p.o doesn't seem to have specific information on Android.

A

@mhsmith
Copy link
Member

mhsmith commented Feb 4, 2025

Thanks for addressing this in Warehouse. Now that the PEP is Final, I think a more appropriate place to maintain this information would be this page, which already contains details of the manylinux tag format.

Although the minimum API level for Python 3.13 is 21, I don't think we should specify any lower bound for the tag format, because there are wheels in circulation for older versions of Python and Android.

@di
Copy link
Member Author

di commented Feb 4, 2025

@mhsmith OK, I filed pypa/packaging.python.org#1801 and marked pypi/warehouse#17549 as blocked on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants