# Python3.13 without GIL thread-safe for all thread-unsafe code? **URL:** \ **Category:** Python Help\ **Created:** [October 4, 2024, 10:22am UTC](https://discuss.python.org/t/python3-13-without-gil-thread-safe-for-all-thread-unsafe-code/66622 "2024-10-04T10:22:13Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ArtemIsmagilov](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/artemismagilov/32/22941_2.png) [@ArtemIsmagilov](https://discuss.python.org/u/ArtemIsmagilov)\ **Post date:** [October 4, 2024, 12:01pm UTC](https://discuss.python.org/t/python3-13-without-gil-thread-safe-for-all-thread-unsafe-code/66622/3 "2024-10-04T12:01:42Z")
> [@What is Thread Safety as applied to Python?](https://discuss.python.org/t/what-is-thread-safety-as-applied-to-python/13685/4): > > Removing the GIL does not make functions thread-safe. Thread-safety relates to this question: If you have a data structure (say, an object, or a list) that is being modified in one thread, can another thread come along and modify it right in the middle of that calculation? Let’s say you have a global variable x which equals 0, and two different threads attempt to increment it using this: x += 1 If incrementing is thread-safe, then you are guaranteed that the result can only be x=2 after the… --- _[View the full topic](https://discuss.python.org/t/python3-13-without-gil-thread-safe-for-all-thread-unsafe-code/66622)._