Thanks to visit codestin.com
Credit goes to github.com

Skip to content

PEP 703: fix some typos #3298

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

Merged
merged 2 commits into from
Aug 21, 2023
Merged

PEP 703: fix some typos #3298

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce91aae
Fix some typos
remilapeyre Aug 18, 2023
0b1a6b7
Update pep-0703.rst
remilapeyre Aug 21, 2023
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
4 changes: 2 additions & 2 deletions pep-0703.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -474,7 +474,7 @@ field.
Default (``0b00``)
""""""""""""""""""

Objects are intitially created in the default state. This is the only
Objects are initially created in the default state. This is the only
state that allows for the quick deallocation code path. Otherwise, the
thread must merge the local and shared reference count fields, which
requires an atomic compare-and-swap.
Expand Down Expand Up @@ -1311,7 +1311,7 @@ The ``PYTHONGIL=0`` override is important because extensions that are
not thread-safe can still be useful in multi-threaded applications. For
example, one may want to use the extension from only a single thread or
guard access by locks. For context, there are already some extensions
that aren not thread-safe even with the GIL, and users already have to
that are not thread-safe even with the GIL, and users already have to
take these sorts of steps.

The ``PYTHONGIL=1`` override is sometimes useful for debugging.
Expand Down