# A Steering Council notice about PEP 703 (Making the Global Interpreter Lock Optional in CPython) **URL:** \ **Category:** Core Development\ **Created:** [July 28, 2023, 8:44pm UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474 "2023-07-28T20:44:43Z")\ **Posts on this page:** 6\ **Page:** 2
**Author:** ![ihearmycalls](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ihearmycalls/32/13905_2.png) [@ihearmycalls](https://discuss.python.org/u/ihearmycalls)\ **Post date:** [August 1, 2023, 6:43am UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474/21 "2023-08-01T06:43:14Z")
I really want to know that if the GIL being removed , my python program will autonomously use the multicore CPUs while i don’t have to use the multiprocess or asynio module? ---
**Author:** ![jeanas](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/jeanas/32/8115_2.png) [@jeanas](https://discuss.python.org/u/jeanas)\ **Post date:** [August 1, 2023, 7:36am UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474/22 "2023-08-01T07:36:06Z")
You have to use the `threading` module (not `multiprocessing` or `asyncio`). ---
**Author:** ![sjatkins](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sjatkins/32/13923_2.png) [@sjatkins](https://discuss.python.org/u/sjatkins)\ **Post date:** [August 1, 2023, 6:47pm UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474/23 "2023-08-01T18:47:27Z")
I don’t see why removing the GIL, which many have fought with for years, need change the language syntax in any way whatsoever. It seems to me a cpython implementation detail. If I am right about that then there is no danger of incompatibility with existing python code. Thus I don’t see why wanting to avoid another Python 2 to Python 3 transition difficulty is relevant. If this sore point of our favorite language can be removed from the implementation and if I am right about no syntax changes being necessary then I say by all means remove it as quickly as possible and have only a period of choosing to run with it remove that is short, say a year, before this sore point is gone from Python forever. I don’t see why anything like 5 years would be necessary. ---
**Author:** ![davidism](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/davidism/32/3295_2.png) [@davidism](https://discuss.python.org/u/davidism)\ **Post date:** [August 1, 2023, 7:05pm UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474/24 "2023-08-01T19:05:37Z")
It’s not changing the syntax, it’s changing the C ABI, which is what native extensions are built against. It is not something that can be changed quickly or without careful planning and review along the way. ---
**Author:** ![davidism](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/davidism/32/3295_2.png) [@davidism](https://discuss.python.org/u/davidism)\ **Post date:** [August 1, 2023, 7:07pm UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474/25 "2023-08-01T19:07:00Z")
Closed on August 1, 2023, 7:07pm UTC ---
**Author:** ![davidism](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/davidism/32/3295_2.png) [@davidism](https://discuss.python.org/u/davidism)\ **Post date:** [August 1, 2023, 7:28pm UTC](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474/26 "2023-08-01T19:28:25Z")
Closing as this is starting to get off topic again. This was meant as an announcement by the SC about the PEP, not further discussion about its feasibility or effects. [Previous page](https://discuss.python.org/t/a-steering-council-notice-about-pep-703-making-the-global-interpreter-lock-optional-in-cpython/30474.md?page=1)