Skip to content

PEP 797: Arbitrary Object Immortalization #4497

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
Some typo fixes.
  • Loading branch information
ZeroIntensity committed Jul 17, 2025
commit 79a7977cc71b13b172ef3b49ff738bc178362ecc
6 changes: 0 additions & 6 deletions peps/pep-0797.rst
Original file line number Diff line number Diff line change
Expand Up @@ -175,10 +175,6 @@ In doing so, an object will release its memory back to CPython's object allocato
allocator is per-interpreter, so it is unsafe to try to release an object's
memory in an interpreter different from the one that created it.

Rationale
=========


Specification
=============

Expand Down Expand Up @@ -419,8 +415,6 @@ The psuedo-code looks like this:
Identifying Immortal Referents
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

In some cases, a

To find the mortal objects that might want to reference an immortal, we have
to make a reasonable assumption about how garbage collection works: in order
for an object to :c:func:`Py_DECREF` another object in its destructor, it
Expand Down
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy