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

Jump to bottom

[3.13] gh-113993: Don't immortalize in PyUnicode_InternInPlace; keep immortalizing in other API (GH-121364) #121854

Merged
merged 1 commit into from
Jul 17, 2024
Merged

[3.13] gh-113993: Don't immortalize in PyUnicode_InternInPlace; keep immortalizing in other API (GH-121364) #121854

merged 1 commit into from
Jul 17, 2024

Commits on Jul 16, 2024

  1. [3.13] pythongh-113993: Don't immortalize in PyUnicode_InternInPlace;… 

    … keep immortalizing in other API (pythonGH-121364)

* Switch PyUnicode_InternInPlace to _PyUnicode_InternMortal, clarify docs

* Document immortality in some functions that take `const char *`

This is PyUnicode_InternFromString;
PyDict_SetItemString, PyObject_SetAttrString;
PyObject_DelAttrString; PyUnicode_InternFromString;
and the PyModule_Add convenience functions.

Always point out a non-immortalizing alternative.

* Don't immortalize user-provided attr names in _ctypes
(cherry picked from commit b4aedb2)

Co-authored-by: Petr Viktorin <encukou@gmail.com>
    @encukou
    encukou committed Jul 16, 2024
    Configuration menu
    Copy the full SHA
    e65f4da View commit details
    Browse the repository at this point in the history