# FR: Allow private runtime config to enable extending without breaking the \`PyConfig\` ABI **URL:** \ **Category:** Core Development\ **Created:** [August 5, 2022, 10:32pm UTC](https://discuss.python.org/t/fr-allow-private-runtime-config-to-enable-extending-without-breaking-the-pyconfig-abi/18004 "2022-08-05T22:32:10Z")\ **Posts on this page:** 1\ **Showing post:** 31
**Author:** ![vstinner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/vstinner/32/15130_2.png) [@vstinner](https://discuss.python.org/u/vstinner)\ **Post date:** [October 2, 2023, 3:57pm UTC](https://discuss.python.org/t/fr-allow-private-runtime-config-to-enable-extending-without-breaking-the-pyconfig-abi/18004/31 "2023-10-02T15:57:31Z")
> [@malemburg](#): > > Before 3.11, I could do this via accessing the global config variables from C. Since 3.11, this no longer works. I’m well aware of the issue, that’s why I created an issue to design a new API to replace the removed API. A limiation of the old API is that it didn’t give access to all of the 66 PyConfig members, but only around 20 members. Also, it was hard to keep them consistent, since nothing prevents setting a global variables after Python initialization. I also have concerns about consistency between PyConfig and sys attributes. That’s why I’m interested by [PEP 726: Module ` __setattr__ ` and ` __delattr__ `](https://peps.python.org/pep-0726/): see [PEP 726: Module \_\_setattr\_\_ and \_\_delattr\_\_ - #22 by vstinner](https://discuss.python.org/t/pep-726-module-setattr-and-delattr/32640/22) discussion. --- _[View the full topic](https://discuss.python.org/t/fr-allow-private-runtime-config-to-enable-extending-without-breaking-the-pyconfig-abi/18004)._