# Naming the Python binary when \`--disable-gil\` is set

**URL:** <https://discuss.python.org/t/naming-the-python-binary-when-disable-gil-is-set/34052>\
**Category:** Core Development\
**Created:** [September 18, 2023, 8:44pm UTC](https://discuss.python.org/t/naming-the-python-binary-when-disable-gil-is-set/34052 "2023-09-18T20:44:22Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [September 19, 2023, 9:58am UTC](https://discuss.python.org/t/naming-the-python-binary-when-disable-gil-is-set/34052/6 "2023-09-19T09:58:32Z")

</div>

cc @hroncok

Fedora packages `python3-debug` (which is _very_ useful for finding bugs!), and I assume we’ll want `python3.13-nogil` to for all the hype. We do want users will want to _test the experimental build_ without hassle, and `/opt` is not really an option for an OS-provided package.

The argument against `python3-nogil` and `python-nogil` sounds good.

* * *

What are your thoughts on printing a colourful warning on interactive mode startup?

---

_[View the full topic](https://discuss.python.org/t/naming-the-python-binary-when-disable-gil-is-set/34052)._