bpo-36763: Use PyConfig_Clear()#14445
bpo-36763: Use PyConfig_Clear()#14445vstinner merged 1 commit intopython:masterfrom vstinner:init_clean
Conversation
vstinner
requested review from
brettcannon,
encukou,
ericsnowcurrently,
ncoghlan and
warsaw
as code owners
vstinner
changed the title
|
This PR depends on PR #14444 to add PyConfig_SetWideStringList(). |
|
The title says this is about |
To be able to use PyConfig_Clear(), as "required" by the PEP 587, you have to use dynamically allocated memory, and so the code has to be modified to use PyConfig_SetWideStringList() instead of static strings. This change depends on PR #14444: we need a PyConfig_SetWideStringList() function, otherwise, it's harder to use set warnoptions and xoptions fields of PyConfig. |
Stop using "static PyConfig", PyConfig must now always use dynamically allocated strings: use PyConfig_SetString(), PyConfig_SetArgv() and PyConfig_Clear().
vstinner
changed the title
|
This change should be backported to 3.8 once PR #14523 is merged. |
|
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Stop using "static PyConfig", PyConfig must now always use dynamically allocated strings: use PyConfig_SetString(), PyConfig_SetArgv() and PyConfig_Clear(). (cherry picked from commit 6731002) Co-authored-by: Victor Stinner <vstinner@redhat.com>
|
GH-14528 is a backport of this pull request to the 3.8 branch. |
Stop using "static PyConfig", PyConfig must now always use dynamically allocated strings: use PyConfig_SetString(), PyConfig_SetArgv() and PyConfig_Clear().
Stop using "static PyConfig", PyConfig must now always use dynamically allocated strings: use PyConfig_SetString(), PyConfig_SetArgv() and PyConfig_Clear().
5 participants
Stop using "static PyConfig", PyConfig must now always use
dynamically allocated strings: use PyConfig_SetString(),
PyConfig_SetArgv() and PyConfig_Clear().
https://bugs.python.org/issue36763