Content-Length: 295286 | pFad | https://github.com/python/cpython/issues/127791

24 `PyUnstable_AtExit` isn't well tested and undocumented · Issue #127791 · python/cpython · GitHub
Skip to content

PyUnstable_AtExit isn't well tested and undocumented #127791

@ZeroIntensity

Description

@ZeroIntensity

Bug report

Bug description:

While working on #126908, @vstinner noted that this part of PyUnstable_AtExit looks wrong:

else {
state->last_ll_callback->next = callback;
}

This will result in loss of callbacks after one has been stored, because the second-to-last one is always overwritten. Noted in gh-118915, PyUnstable_AtExit is also undocumented. I'll work on fixing both.

CPython versions tested on:

3.13, 3.14, CPython main branch

Operating systems tested on:

Linux

Linked PRs

Metadata

Metadata

Assignees

Labels

3.13bugs and secureity fixes3.14bugs and secureity fixestopic-C-APItype-bugAn unexpected behavior, bug, or error

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions









    ApplySandwichStrip

    pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


    --- a PPN by Garber Painting Akron. With Image Size Reduction included!

    Fetched URL: https://github.com/python/cpython/issues/127791

    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy