There is no python3-freethreading, hence there is no /usr/bin/python3t and there is no "system" freethreading interpreter.

python3.14-freethreading is another, non-system Python interpreter, same as python3.15-freethreading.

Yes there is? Sure it's only a provides and not the actual package name, but it's there.

On my Fedora 43 system, "dnf install python3-freethreading" pulls in python3.14-freethreading. I'm not sure why it doesn't follow the convention that we used for the python3-debug package, but saying there's no "system freethreading python interpreter" is at least wrong on a basic level, just like how we have a system Python "debug" interpreter too.

So the python3-freethreading Provide is actually an oversight based on automatic provides generators, sigh.

The difference between the system Python debug interpreter (which we DO have) is that the debug interpreter shares a lot of things with the system interpreter (e.g., pure Python standard library, or sys.path). If you install python3-foo, you can import it from the Python debug interpreter.

Contrary to that, the freethreding interpeter is "isolated" and has nothing in common with the system interpreter, sans the major version and the fact that we build it from the same SRPM to make our work simpler. You can even install python3.14-freethreding without python3 or install a different patch version. If you install python3-foo, you cannot import it from the freethreading Python interpreter, same way you cannot import it from python3.12.

Does that explain the differences?

So it doesn't use the same python sitelib and sitearch path as the regular interpreter either?

(In reply to Neal Gompa from comment #4)
> So it doesn't use the same python sitelib and sitearch path as the regular
> interpreter either?

Right, it uses e.g. /usr/lib/python3.14t and /usr/lib64/python3.14t.

It has been a month without more discussion, so I am closing this now. Feel free to discuss this on the Fedora Python devel mailing list.