Skip to content
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

PEP 683: Add a PEP for immortal objects #2320

Merged
merged 34 commits into from
Feb 15, 2022
Merged

PEP 683: Add a PEP for immortal objects #2320

Changes from 1 commit
Commits
Show all changes
34 commits
Select commit Hold shift + click to select a range
b396af6
Add a PEP for immortal objects.
ericsnowcurrently Feb 11, 2022
19991dc
Move the mention of the python-dev thread.
ericsnowcurrently Feb 11, 2022
49a78f0
Add some open questions.
ericsnowcurrently Feb 11, 2022
4241d1b
Py_SETREF() -> Py_SET_REFCNT().
ericsnowcurrently Feb 11, 2022
56e7174
Update the documentation section.
ericsnowcurrently Feb 11, 2022
9589df7
Update the PEP header.
ericsnowcurrently Feb 11, 2022
0cbd50b
Fold "Proposal" into "Specification".
ericsnowcurrently Feb 11, 2022
413f465
Update the "Performance" section.
ericsnowcurrently Feb 11, 2022
4099282
Drop unused sections.
ericsnowcurrently Feb 11, 2022
02260bf
Fix typos.
ericsnowcurrently Feb 11, 2022
9126cc6
Add an open issue.
ericsnowcurrently Feb 11, 2022
850bd8d
Enumerate objects that will be immortalized.
ericsnowcurrently Feb 11, 2022
57b536c
Update the "Motivation" section.
ericsnowcurrently Feb 11, 2022
7437848
Clarify how we will probably identify immortal objects.
ericsnowcurrently Feb 11, 2022
016f895
Give examples of what are global objects.
ericsnowcurrently Feb 11, 2022
904868d
Assign a PEP number.
ericsnowcurrently Feb 11, 2022
a048b57
Update the PEP header.
ericsnowcurrently Feb 11, 2022
7d5401c
Drop the "Concerns" section.
ericsnowcurrently Feb 11, 2022
5340a17
Drop the "How to Teach This" section.
ericsnowcurrently Feb 11, 2022
63caa44
Drop an unnecessary aside.
ericsnowcurrently Feb 11, 2022
ab6943e
Add a rejected idea.
ericsnowcurrently Feb 11, 2022
743c753
Update CODEOWNERS.
ericsnowcurrently Feb 11, 2022
92fc5d4
Do not use an inline link for the implementation PR.
ericsnowcurrently Feb 11, 2022
4e1f5fc
Add a link to the docs explaining refcounts.
ericsnowcurrently Feb 11, 2022
c94ef99
Drop the PEP delegate.
ericsnowcurrently Feb 11, 2022
4667e82
Don't use footnotes for plain links.
ericsnowcurrently Feb 11, 2022
d6a88f3
Update Eddie's email address.
ericsnowcurrently Feb 14, 2022
6816e8f
Change the type.
ericsnowcurrently Feb 14, 2022
db4a703
Fix the References section.
ericsnowcurrently Feb 15, 2022
77bd7ee
Mention how Py_SET_REFCNT() won' change the refcount.
ericsnowcurrently Feb 15, 2022
f8cf975
Mention that GC state also impacts true immutability for containers.
ericsnowcurrently Feb 15, 2022
bb17abb
Emphasize the impact on app scalability.
ericsnowcurrently Feb 15, 2022
6eb4b36
Explain cleanup in the Specification section.
ericsnowcurrently Feb 15, 2022
aa5f14e
sys.gettotalrefcount() is not affected.
ericsnowcurrently Feb 15, 2022
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
Change the type.
  • Loading branch information
@ericsnowcurrently
ericsnowcurrently committed Feb 14, 2022
commit 6816e8f45b91a36ff6bb27e07285c411cd4c3505
2 changes: 1 addition & 1 deletion pep-0683.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Title: Immortal Objects, Using a Fixed Refcount
Author: Eric Snow <ericsnowcurrently@gmail.com>, Eddie Elizondo <eduardo.elizondorueda@gmail.com>
Discussions-To: python-dev@python.org
Copy link
Member

Choose a reason for hiding this comment

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

Please update the PEP with a link to the actual thread once you create it, so it is easy for others to find without a lot of guessing and Googling.

Also, there are a smattering of relatively non-critical editing issues (aside from the title containing a comma, which is a bit irregular), but as this was merged just as I got to it, I'm a bit late to the party now so if needed, I can make a separate PR fixing those (though they aren't terribly critical).

Status: Draft
Type: Informational
Type: Standards Track
Content-Type: text/x-rst
Created: 10-Feb-2022
Python-Version: 3.11
Expand Down