# PEP 703: Making the Global Interpreter Lock Optional (3.12 updates) **URL:** \ **Category:** PEPs\ **Created:** [May 4, 2023, 6:22pm UTC](https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional-3-12-updates/26503 "2023-05-04T18:22:11Z")\ **Posts on this page:** 1\ **Showing post:** 130
**Author:** ![laike9m](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/laike9m/32/142_2.png) [@laike9m](https://discuss.python.org/u/laike9m)\ **Post date:** [June 16, 2023, 7:59am UTC](https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional-3-12-updates/26503/130 "2023-06-16T07:59:10Z")
With respects to the technical cocerns people brought up, I think it’s all agreed that the opportunity loss of rejecting nogil is too large to even quantify. An energised community with lots of problems to solve, is (IMHO) better than a disappointed community with no problem to solve. I do agree with Mark that picking a long-term strategy is very important. > [@A fast, free threading Python](https://discuss.python.org/t/a-fast-free-threading-python/27903): > > PEP 703 is touted as offering free-threading in CPython at almost no performance cost. But building a fast, free threading CPython isn’t as simple as just accepting a PEP. So, what would take to have a fast, free threading Python? The short answer: A lot of developer time, which means a substantial amount of money from somewhere. This can happen, but there needs to be sufficient commercial interest in free-threading Python. The long answer: There are three important aspects of Python to cons… --- _[View the full topic](https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional-3-12-updates/26503)._