Skip to content

use nested list for WHEEL details + other minor tweaks #1955

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.

Sign up for GitHub

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
+15 −15
Draft

use nested list for WHEEL details + other minor tweaks #1955

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
30 changes: 15 additions & 15 deletions source/specifications/binary-distribution-format.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -206,21 +206,21 @@ in both fields) consist of:
Tag: py3-none-any
Build: 1

#. ``Wheel-Version`` is the version number of the Wheel specification.
#. ``Generator`` is the name and optionally the version of the software
that produced the archive.
#. ``Root-Is-Purelib`` is true if the top level directory of the archive
should be installed into purelib; otherwise the root should be installed
into platlib.
#. ``Tag`` is the wheel's expanded compatibility tags; in the example the
filename would contain ``py2.py3-none-any``.
#. ``Build`` is the build number and is omitted if there is no build number.
#. A wheel installer should warn if Wheel-Version is greater than the
version it supports, and must fail if Wheel-Version has a greater
major version than the version it supports.
#. Wheel, being an installation format that is intended to work across
multiple versions of Python, does not generally include .pyc files.
#. Wheel does not contain setup.py or setup.cfg.
#. ``Wheel-Version`` is the version number of the Wheel specification.
Copy link
Contributor Author

@merwok merwok Nov 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

github rendering shows that this is interpreted as part of the code block instead of creating a nested list. to be fixed.

#. ``Generator`` is the name and optionally the version of the software
that produced the archive.
#. ``Root-Is-Purelib`` is true if the top level directory of the archive
should be installed into purelib; otherwise the root should be installed
into platlib.
#. ``Tag`` is the wheel's expanded compatibility tags; in the example the
filename would contain ``py2.py3-none-any``.
#. ``Build`` is the build number and is omitted if there is no build number.
#. A wheel installer should warn if ``Wheel-Version`` is greater than the
version it supports, and must fail if ``Wheel-Version`` has a greater
major version than the version it supports.
#. Wheel files, being an installation format that is intended to work across
multiple versions of Python, do not generally include ``.pyc`` files.
#. Wheels files do not contain ``pyproject.toml``, ``setup.py`` or ``setup.cfg``.

This version of the wheel specification is based on the distutils install
Copy link
Contributor Author

@merwok merwok Nov 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should say sysconfig install schemes.

schemes and does not define how to install files to other locations.
Expand Down
Loading