add Python dev env

[pantheraleo-7]

Tying the new python environment feature to Pip dev env doesn't make sense. Nor adding other dev envs like Uv to it (at least to me).

So I've added a Python dev env with all the possible [default] paths a python interpreter can be located at on macOS (that I can think of). So if any of the paths (i.e. python interpreters) exist, we get the feature enabled.

If I knew Swift, I would made the following changes (alas!):

• Use the [available] paths in a dropdown list here:
• hide the 'Delete Folder' and 'Delete Contents' button across the Python dev env

One potential related feature could be that when we go to, say, pyenv dev env, we use the pyenv paths to list the python packages and similarly for others like uv, etc. While the Python dev env will continue to have all the paths plus a custom path picker.

[EReaso]

Upon running which python3 in my terminal, I get /Library/Frameworks/Python.framework/Versions/3.14/bin/python3, which I think you forgot.

[pantheraleo-7]

That's a system-wide installation, probably by the python.org installer, so it should be symlinked to /usr/local/bin/python* or similar. Can you confirm?

[EReaso]

This seems to be the case.

[pantheraleo-7]

Yeah, so /Library/Frameworks/Python.framework is not the "user-facing" location. Every system-wide Python installation [should] install there (on macOS). What concerns us are /usr/bin and /usr/local/bin.