Friday, June 26, 2026

Tracking down 11, 12, 14, and 13 Python "stuff"

python3.11-tk Python interpreter Yes, that is part of it. 3.11 was from 2025, but this is 2026. Linux Mint Cinnamon 22.3 is using some 12 version. I was trying to get "14" on the PyCharm I had, but due to a "sandbox" issue, I couldn't. I completely removed the flatpak Pycharm I was using which was determined as a sandbox for some reason, and then I put on tar installation and it worked. It automatically recognized the 12 version and I could use customtkinter in PyCharm. Yes, now I remember the sequence much more clearly. Here's what happened: Originally (2025): You had a Flatpak installation of PyCharm. Because Flatpak runs applications in a sandbox, it couldn't properly see the Python installations on your system. You were trying to use Python 3.14, but PyCharm either couldn't find it or couldn't use it correctly because of the sandbox. The fix: You removed the Flatpak version of PyCharm. You installed the tarball version (through JetBrains Toolbox or directly). That version was no longer sandboxed and could access the system Python. On Linux Mint 22.3: PyCharm automatically detected the system Python 3.12 interpreter. You installed customtkinter into that interpreter (or its virtual environment). Everything worked normally, and you decided you were happy using Python 3.12 instead of chasing 3.14. Now you're on PeppermintOS Trixie, which means we need to determine whether you're back in the same situation. I am now on PeppermintOS Trixie. I typed in Pycharm with Python 12 and it gave back nothing. If typing something like: pycharm or searching for "PyCharm" returns nothing, there are a few possibilities. First, let's determine whether PyCharm is installed at all. In a terminal, try these commands one at a time: which pycharm which pycharm-community which idea Then check whether Python 3.12 exists: python3 --version python3.12 --version Also see if the executable is somewhere on your system: find ~ -iname "pycharm*" 2>/dev/null or, if you installed it system-wide: find /opt -iname "pycharm*" 2>/dev/null Since you switched to PeppermintOS Remember that changing distributions does not carry over installed applications unless you reused the same installation. If this is a fresh Peppermint installation, you'll likely need to reinstall: PyCharm your virtual environments packages like python-chess and customtkinter Your project files are only still there if they're on a partition or home directory that you kept. Can you tell me exactly what you typed? When you wrote: "I typed in Pycharm with Python 12 and it gave back nothing." Did you mean: you searched the application menu for "PyCharm"? you typed pycharm in a terminal? or you were searching inside PyCharm for a Python 3.12 interpreter? Also, please post the output of: python3 --version which python3 which pycharm That will tell us where things stand. Thought for a few seconds Yes. From what I can recall, the issue wasn't that Python 3.12 itself was missing—it was that after switching environments, PyCharm wasn't using a Python installation with the components you needed. More specifically: PyCharm ended up using /usr/bin/python. Running your customtkinter test failed because it couldn't find tkinter (ModuleNotFoundError: No module named 'tkinter'). You preferred to run installation commands in the normal terminal, not the PyCharm terminal, and we discussed installing the missing python3.11-tk package there. Now you've switched to PeppermintOS Trixie, so we may be dealing with a different issue. When you said: "I typed in Pycharm with Python 12 and it gave back nothing." it reminds me of another problem we had recently: PyCharm couldn't see or select the Python interpreter you wanted. Can you tell me exactly where you typed "Python 12"? In PyCharm → Add Interpreter? In the application launcher? In a terminal? Somewhere else? That will help determine whether this is the same interpreter-detection problem or something new. python3.11-tk Python interpreter Yes, that is part of it. 3.11 was from 2025, but this is 2026. Linux Mint Cinnamon 22.3 is using some 12 version. I was trying to get "14" on the PyCharm I had, but due to a "sandbox" issue, I couldn't. I completely removed the flatpak Pycharm I was using which was determined as a sandbox for some reason, and then I put on tar installation and it worked. It automatically recognized the 12 version and I could use customtkinter in PyCharm. Yes, now I remember the sequence much more clearly. Here's what happened: Originally (2025): You had a Flatpak installation of PyCharm. Because Flatpak runs applications in a sandbox, it couldn't properly see the Python installations on your system. You were trying to use Python 3.14, but PyCharm either couldn't find it or couldn't use it correctly because of the sandbox. The fix: You removed the Flatpak version of PyCharm. You installed the tarball version (through JetBrains Toolbox or directly). That version was no longer sandboxed and could access the system Python. On Linux Mint 22.3: PyCharm automatically detected the system Python 3.12 interpreter. You installed customtkinter into that interpreter (or its virtual environment). Everything worked normally, and you decided you were happy using Python 3.12 instead of chasing 3.14. Now you're on PeppermintOS Trixie, which means we need to determine whether you're back in the same situation. The first thing I'd like to know is how you installed PyCharm on Peppermint. Was it: Flatpak JetBrains Toolbox Downloaded tar.gz from JetBrains APT package Something else? If it's Flatpak again, I'd immediately suspect the same sandbox problem. Also, could you run these two commands? which pycharm and python3 --version If which pycharm returns nothing, that's okay—it tells us PyCharm isn't on your PATH, which helps narrow down how it was installed. Python 3.13.5 (LOL, there's my 13?) Why did Linux Mint skip from 12 to 14? 😄 That is a good catch. The answer is: Linux Mint didn't actually skip from 3.12 to 3.14. Here's what likely happened: Linux Mint 22.x is based on a version of Ubuntu whose default Python is 3.12. At some point you installed Python 3.14 yourself (or from a PPA or source), which is why you were trying to get PyCharm to recognize it. Now that you're on PeppermintOS Trixie (which is based on a newer Debian release), the default system Python is 3.13.5. So your timeline is probably: Linux Mint 22.3 → Python 3.12.x (system default) You manually installed 3.14 and tried to use it in PyCharm. Flatpak PyCharm couldn't see it because of sandboxing. Tarball PyCharm worked with the system Python 3.12. Now PeppermintOS Trixie ships with Python 3.13.5 as the default. In other words, the operating systems didn't "jump" from 3.12 to 3.14—you introduced 3.14 yourself. The new operating system simply comes with 3.13. You can verify what you have installed with: python3 --version python3.13 --version python3.14 --version ls /usr/bin/python3* I'm actually pleased to see 3.13.5 on your Peppermint system. It means you probably don't need to chase a newer interpreter this time. We can just point PyCharm at Python 3.13 and install python3-tk, python3-venv, python3-pip, python-chess, and customtkinter in that environment. That should give you essentially the same smooth setup you ended up with on Linux Mint.

No comments:

Post a Comment