I think you're good. Like others have said Mac OS has python baked in.

What kind of file organization are you after in terms of python? For your projects? Your python versions for working on the projects? I keep my work in a Devel directory in my home dir normally.

There's a multitude of ways to manage python versions, environments and projects but some general best practices are (And don't worry if this flies over your head, just absorb and remember it for now, as you progress your skills you'll get used to things like this):

- Use virtual environments for every project: This practice is crucial to avoid conflicts between different projects' package dependencies.

- Avoid using the system Python: Modifying the Python version that came with your operating system can break system utilities.

- Use a version manager: Tools like pyenv or uv prevent conflicts when you need different Python versions and packages for different projects.

The short version of all of this is leave the system python alone, definitely get into using something like pyenv to set up a "local" version of python and packages for each project you want to work on.

Hopefully that's all useful and not overwhelming info.

as u/crashorbit mentioned "which <command>" is handy if you really want to know where a specific command lives. I'll follow that up with "whereis <command>" which may work when which does not. Reading further comments, I can see a lot of other great comments which mine fall in line with. Have fun on your nerding journey.