diff options
| author | Cristián Maureira-Fredes <Cristian.Maureira-Fredes@qt.io> | 2024-06-03 14:49:48 +0200 |
|---|---|---|
| committer | Cristián Maureira-Fredes <cristian.maureira-fredes@qt.io> | 2024-08-13 10:49:51 +0200 |
| commit | d0b68335d7eee53c0d2cfa7f1c67e5adc7bab32a (patch) | |
| tree | 711e35ae67525f6e6f2df7bf4453c9d6b9b65e39 /examples/widgetbinding/doc/widgetbinding.pyproject | |
| parent | 8d6ad7ed46552bf7f06fc667a936673e13b62262 (diff) | |
Remove the usage of Py_SetProgramName
Py_SetProgramName is deprecated since 3.11 and there is no planned
direct replacement. There is a recommendation of using PyConfig,
which implies a more verbose approach, so we drop the lines
instead of replacing it.
This:
Py_SetProgramName(L"module-test");
can be replaced by:
PyStatus status;
PyConfig config;
PyConfig_InitPythonConfig(&config);
status = PyConfig_SetString(&config, &config.program_name, program_name);
if (PyStatus_Exception(status)) {
goto exception;
}
status = Py_InitializeFromConfig(&config);
if (PyStatus_Exception(status)) {
goto exception;
}
exception:
PyConfig_Clear(&config);
Py_ExitStatusException(status);
Note: PyConfig's approach is not part of the Stable ABI,
meaning it will not be possible to use it once Py_SetProgramName
is removed in 3.13
Change-Id: I0734d502469ae4f28f4c211bdfbfdbeae82b1375
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
Diffstat (limited to 'examples/widgetbinding/doc/widgetbinding.pyproject')
0 files changed, 0 insertions, 0 deletions
