Skip to content

PEP 817: Final set of pre-split updates#4867

Open
mgorny wants to merge 1 commit into
python:mainfrom
wheelnext:pep-817-update
Open

PEP 817: Final set of pre-split updates#4867
mgorny wants to merge 1 commit into
python:mainfrom
wheelnext:pep-817-update

Conversation

@mgorny
Copy link
Copy Markdown
Contributor

@mgorny mgorny commented Mar 19, 2026

  • Change is either:
    • To a Draft PEP
    • To an Accepted or Final PEP, with Steering Council approval
    • To fix an editorial issue (markup, typo, link, header, etc)
  • PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

This is a set of updates to PEP 817 that were prepared prior to the decision to split it into smaller PEPs. We do not intend to pursue PEP 817 in this updated form. However, we would like to get the changes committed to the repository so that the history of changes is not lost.

The changes include refocusing of the security details, some clarifications, tool behavior outlines and update for the images to respect dark theme.

We are not marking the PEP as withdrawn, as our current plan is to eventually replace the specification part with an index listing the split PEPs.


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

This is a set of updates to PEP 817 that were prepared prior to the
decision to split it into smaller PEPs.  We do not intend to pursue
PEP 817 in this updated form.  However, we would like to get the changes
committed to the repository so that the history of changes is not lost.

The changes include refocusing of the security details, some
clarifications, tool behavior outlines and update for the images to
respect dark theme.

We are not marking the PEP as withdrawn, as our current plan is to
eventually replace the specification part with an index listing the
split PEPs.

Signed-off-by: Michał Górny <mgorny@quansight.com>
@mgorny mgorny requested review from dstufft and warsaw as code owners March 19, 2026 16:58
Copy link
Copy Markdown
Contributor

@rgommers rgommers left a comment

Choose a reason for hiding this comment

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

This was reviewed in detail by multiple co-authors before opening this PR. It contains important clarifications, as well as the diagram that multiple reviewers found really helpful.

PEP editors, can this please be merged?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This shows up in a blockquote:

Image

Unindent the block to fix:

.. figure:: pep-0817/avx512_gromacs_benchmark.svg
    :alt: A bar graph comparing GROMACS performance (in ns/day) with
          various targets. The first two bars are labeled "yum
          (2018.8)" and "generic (SSE2)", reach about 1.0 ns/day and
          are both marked as "SSE2". The next bar is labeled
          "ivybridge" ("AVX") and reaches almost 1.5 ns/day. Two
          following bars are labeled "haswell" and "broadwell" (both
          "AVX2") and exceed 1.5 ns/day slightly. The last two bars
          are labeled "skylake_avx512" and "cascadelake" (both
          "AVX512") and reach almost 2.0 ns/day.

    Performance of GROMACS 2020.1 built for different generations of
    CPUs. Vertical axis shows performance expressed in ns/day, a
    GROMACS-specific measure of simulation speed (higher is better).

Compiling GROMACS_ for architectures that can exploit the AVX-512
instructions supported by the Intel Cascade Lake microarchitecture
gives an additional 18% performance improvement relative to using
AVX2 instructions, with a speedup of about 70% compared to a generic
GROMACS installation with only SSE2.

— `archspec: A library for detecting, labeling, and reasoning about
microarchitectures
<https://tgamblin.github.io/pubs/archspec-canopie-hpc-2020.pdf>`__

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'll note that that's how it came out of the last review, rather than being introduced here: https://peps.python.org/pep-0817/#runtime-cpu-dispatching.

Might be improve-able indeed though, worth trying.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It is a blockquote.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ah right, then I suggest just moving the source ("—archspec: A library for detecting, labeling, and reasoning about microarchitectures") bit outside the blockquote.

Comment thread peps/pep-0817.rst

.. figure:: pep-0817/conceptual_diagram_installers.svg
:target: _images/conceptual_diagram_installers.svg
:alt: TODO.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please add alt text.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for the quick response @hugovk. We'll update.

Comment thread peps/pep-0817.rst
Comment on lines +1068 to +1072
.. figure:: pep-0817/conceptual_diagram_installers.svg
:target: _images/conceptual_diagram_installers.svg
:alt: TODO.

A conceptual diagram of installing a wheel.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Unindent to remove blockquote:

Image
Suggested change
.. figure:: pep-0817/conceptual_diagram_installers.svg
:target: _images/conceptual_diagram_installers.svg
:alt: TODO.
A conceptual diagram of installing a wheel.
.. figure:: pep-0817/conceptual_diagram_installers.svg
:target: _images/conceptual_diagram_installers.svg
:alt: TODO.
A conceptual diagram of installing a wheel.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This looks okay in dark mode:

Image

But the lines and a lot of text are invisible or hard to read in light:

Image

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@mgorny I thought we fixed the light/dark mode behavior?

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