Why does python "forget" the path to the system python?

I'm on a Mac with Apple silicon, using zsh, and python 3.11. I installed python "system" with homebrew, which automatically installs python 3.11. After installation, python3.11 works, "python" alone works, and pip works. Meanwhile, python3 doesn't work, pip3 doesn't work, and pip3.11 works. Everything's fine. Then, I restart the terminal or zsh. Python 3.11 continues to work, and pip3.11 continues to work, but "python" and "pip" alone stop working, while "python3" and "pip3" start working. "python" stops working to the extent that I can't even manage packages globally.<br><br>Is there a way to avoid this?<br>Do I have to install pipx?<br>Can I do all of this without using pip and pipx, but only with conda?<br>Is there a way to run pip3.11 without using -m but without using pip3.11 (this is the only version that works in both cases)?<br>If I start a venv and run the command "python" once in the shell, do I have to manually deactivate every time?<br>How do I make this more intuitive and more automatic?<br><br>I apologize for this; this question is all over the place because I'm genuinely totally confused. Like for example, what is the difference between "python" and "python3"? Apparently "python" is a cli that can run python 2 and python 3, which is why python 2 is widely sunset.<br><br>I would really appreciate any help at all. Thanks!