# Thread safety now and in the future (no-gil)

**URL:** <https://discuss.python.org/t/thread-safety-now-and-in-the-future-no-gil/104297>\
**Category:** Threading\
**Created:** [October 10, 2025, 6:12pm UTC](https://discuss.python.org/t/thread-safety-now-and-in-the-future-no-gil/104297 "2025-10-10T18:12:12Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![jbosboom](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@jbosboom](https://discuss.python.org/u/jbosboom)\
**Post date:** [October 10, 2025, 10:34pm UTC](https://discuss.python.org/t/thread-safety-now-and-in-the-future-no-gil/104297/9 "2025-10-10T22:34:09Z")

</div>

As a concrete example of the confusion, the Library and Extension FAQ’s question [What kinds of global value mutation are thread-safe?](https://docs.python.org/3/faq/library.html#what-kinds-of-global-value-mutation-are-thread-safe) actually lists operations on objects of built-in type that are guaranteed to be atomic.

(See also [another post of mine](https://discuss.python.org/t/pre-pep-safe-parallel-python/103636/30) where I mention some other guarantees that aren’t documented.)

---

_[View the full topic](https://discuss.python.org/t/thread-safety-now-and-in-the-future-no-gil/104297)._