Skip to content

PEP 583: Fix Sphinx warnings #4808

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

Open
Secrus wants to merge 1 commit into
base: main
Choose a base branch
from
Open

PEP 583: Fix Sphinx warnings #4808

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
17 changes: 2 additions & 15 deletions peps/pep-0583.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -312,7 +312,7 @@ implementers.
A happens-before race that's not a sequentially-consistent race
---------------------------------------------------------------

From the POPL paper about the Java memory model [#JMM-popl].
From the POPL paper about the Java memory model [#JMM-popl]_.
Copy link
Contributor

@SpecLad SpecLad Feb 3, 2026

Choose a reason for hiding this comment

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

FYI, there's another ill-formed reference to this footnote on line 367.


Initially, ``x == y == 0``.

Expand Down Expand Up @@ -552,7 +552,7 @@ that, and Python may not need those security guarantees anyway.
Restrict reorderings instead of defining happens-before
--------------------------------------------------------

The .NET [#CLR-msdn] and x86 [#x86-model] memory models are based on
The .NET [#CLR-msdn]_ and x86 [#x86-model]_ memory models are based on
defining which reorderings compilers may allow. I think that it's
easier to program to a happens-before model than to reason about all
of the possible reorderings of a program, and it's easier to insert
Expand Down Expand Up @@ -784,10 +784,6 @@ References
lots of examples of compiler/processor optimizations and the
strange program behaviors they can produce.

.. [#Cpp0x-memory-model] N2480: A Less Formal Explanation of the
Proposed C++ Concurrency Memory Model, Hans Boehm
(http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2480.html)

.. [#CLR-msdn] Memory Models: Understand the Impact of Low-Lock
Techniques in Multithreaded Apps, Vance Morrison
(http://msdn2.microsoft.com/en-us/magazine/cc163715.aspx)
Expand All @@ -804,15 +800,6 @@ References

.. [#slots] __slots__ (http://docs.python.org/ref/slots.html)

.. [#] Alternatives to SC, a thread on the cpp-threads mailing list,
which includes lots of good examples.
(http://www.decadentplace.org.uk/pipermail/cpp-threads/2007-January/001287.html)

.. [#safethread] python-safethread, a patch by Adam Olsen for CPython
that removes the GIL and statically guarantees that all objects
shared between threads are consistently
locked. (http://code.google.com/p/python-safethread/)


Acknowledgements
================
Expand Down
Loading