# A fast, free threading Python

**URL:** <https://discuss.python.org/t/a-fast-free-threading-python/27903>\
**Category:** Ideas\
**Created:** [June 15, 2023, 3:28pm UTC](https://discuss.python.org/t/a-fast-free-threading-python/27903 "2023-06-15T15:28:04Z")\
**Posts on this page:** 1\
**Showing post:** 99

<div class="post-metadata">

**Author:** ![carljm](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/carljm/32/959_2.png) [@carljm](https://discuss.python.org/u/carljm)\
**Post date:** [July 7, 2023, 11:53pm UTC](https://discuss.python.org/t/a-fast-free-threading-python/27903/99 "2023-07-07T23:53:54Z")

</div>

> [@guido](#):
>
> it would be great if Meta or another tech company could spare some engineers with established CPython internals experience to help the core dev team with this work.

We’ve had a chance to discuss this internally with the right people. Our team believes in the value that nogil will provide, and we are committed to working collaboratively to improve Python for everyone.

If PEP 703 is accepted, Meta can commit to support in the form of three engineer-years (from engineers experienced working in CPython internals) between the acceptance of PEP 703 and the end of 2025, to collaborate with the core dev team on landing the PEP 703 implementation smoothly in CPython and on ongoing improvements to the compatibility and performance of nogil CPython.

---

_[View the full topic](https://discuss.python.org/t/a-fast-free-threading-python/27903)._