# PEP 703: Making the Global Interpreter Lock Optional

**URL:** <https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional/22606>\
**Category:** PEPs\
**Created:** [January 10, 2023, 4:08pm UTC](https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional/22606 "2023-01-10T16:08:09Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![gregington](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@gregington](https://discuss.python.org/u/gregington)\
**Post date:** [January 11, 2023, 2:47am UTC](https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional/22606/10 "2023-01-11T02:47:47Z")

</div>

The **Python Critical Sections** part of the document describes how threads can only hold a single lock at a time to avoid deadlocks, where existing locks are released when a new lock is acquired.

If multiple locks are taken to ensure mutual consistency across multiple resources, is it possible that a second thread can acquire a released lock and make changes that are inconsistent with the work performed by the first thread? At first glance, this has the potential to violate program correctness in a multithreaded environment.

---

_[View the full topic](https://discuss.python.org/t/pep-703-making-the-global-interpreter-lock-optional/22606)._
