You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm assuming the following PEP is being left open until the field is actually removed in 3.14 (which could be implemented on main now that 3.13 is in beta):
I'm not sure what to do with PEP 699. AFAIK, the field has been repurposed to mean something else for the most part by now. All that's left should be to remove the code guaranteeing the increments in 3.14 and it should be done?
@ericsnowcurrently#3824 marks PEP 683 as Final. The edits to the acceptance criteria need to be confirmed as correct, as do the two unchecked checkboxes.
I'm wondering if it might be worth adding more detail on immortal objects to a new subheading in https://docs.python.org/3/c-api/refcounting.html though, as the best canonical doc reference I could find in the reference docs is to the term reference count which really just mentions immortal objects rather than explaining them. A glossary entry referencing that new subsection would also be helpful.
The two explanatory links in the C API docs go to the PEP, which is about to be marked as no longer to be trusted as living documentation.
I'm wondering if it might be worth adding more detail on immortal objects to a new subheading in https://docs.python.org/3/c-api/refcounting.html though, as the best canonical doc reference I could find in the reference docs is to the term reference count which really just mentions immortal objects rather than explaining them. A glossary entry referencing that new subsection would also be helpful.
The two explanatory links in the C API docs go to the PEP, which is about to be marked as no longer to be trusted as living documentation.
Regarding PEP 687, you can see the implementation status on python/cpython#103092. Only the faulthandler module is left and I'm not sure that's worth waiting to mark the PEP as final.
Activity
encukou commentedon Jun 5, 2024
PEP-687 just got "feature-complete" for 3.13 beta 2, thanks to Eric and Erlend. AFAIK there's more cleanup to do.
PEP-683 needs updating the TODOs.
Fidget-Spinner commentedon Jun 5, 2024
I'm not sure what to do with PEP 699. AFAIK, the field has been repurposed to mean something else for the most part by now. All that's left should be to remove the code guaranteeing the increments in 3.14 and it should be done?
ericsnowcurrently commentedon Jun 5, 2024
Yes, 683 is should be marked "final".
ncoghlan commentedon Jun 6, 2024
@ericsnowcurrently #3824 marks PEP 683 as Final. The edits to the acceptance criteria need to be confirmed as correct, as do the two unchecked checkboxes.
I'm wondering if it might be worth adding more detail on immortal objects to a new subheading in https://docs.python.org/3/c-api/refcounting.html though, as the best canonical doc reference I could find in the reference docs is to the term
reference countwhich really just mentions immortal objects rather than explaining them. A glossary entry referencing that new subsection would also be helpful.The two explanatory links in the C API docs go to the PEP, which is about to be marked as no longer to be trusted as living documentation.
ericsnowcurrently commentedon Jun 12, 2024
Let's discuss this on python/cpython#120426.
ericsnowcurrently commentedon Jun 12, 2024
Regarding PEP 687, you can see the implementation status on python/cpython#103092. Only the faulthandler module is left and I'm not sure that's worth waiting to mark the PEP as final.
hugovk commentedon Jun 15, 2026
I think we're all done now with #4986. 🚀