# PEP 741: Python Configuration C API (second version)

**URL:** <https://discuss.python.org/t/pep-741-python-configuration-c-api-second-version/45403>\
**Category:** PEPs\
**Created:** [February 8, 2024, 6:48pm UTC](https://discuss.python.org/t/pep-741-python-configuration-c-api-second-version/45403 "2024-02-08T18:48:30Z")\
**Posts on this page:** 1\
**Showing post:** 77

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [June 4, 2024, 1:46pm UTC](https://discuss.python.org/t/pep-741-python-configuration-c-api-second-version/45403/77 "2024-06-04T13:46:45Z")

</div>

The PEP says:

> Previously, it was possible to set directly global configuration variables:
> 
> ```
> Py_OptimizeFlag
> Py_VerboseFlag
> Py_DebugFlag
> Py_InspectFlag
> Py_DontWriteBytecodeFlag
> 
> ```
> 
> But these configuration flags were deprecated in Python 3.12 and are scheduled for removal in Python 3.14.

I see these were deprecated in [#93103](https://github.com/python/cpython/issues/93103) (3.12) and the removal schedule was set in [#106538](https://github.com/python/cpython/pull/106538) (3.13), but I could not find a reason to use the shortest deprecation period allowed by [PEP 387](https://peps.python.org/pep-0387/#making-incompatible-changes).  
Note PEP 387 says:

> If the deprecated feature is replaced by a new one, it should generally be removed only after the last Python version _without_ the new feature reaches end of support.

If these need a replacement but we’re only adding it now, shouldn’t the removals be postponed?

---

_[View the full topic](https://discuss.python.org/t/pep-741-python-configuration-c-api-second-version/45403)._