Python versions mess not able to successfully install packages anymore

I am using Python version 3.11 with MacOS Ventura 13.1 (M1 chip) and cannot successfully install packages anymote. Upon installing them (apparently successfully) Python does not find them and is thus also not able to uninstall them.

I have a lot of research related and thus really important packages installed under a folder opt/homebrew/lib/python3.10/site-packages/

How can I get them to work with 3.11?
And a few more questions:
a) For some reason pip install doesn't work anymore, pip3 install does however, is that normal?
b) whenever I install something it says:

[notice] A new release of pip available: 22.3.1 -> 23.0
[notice] To update, run: python3.11 -m pip install --upgrade pip
user@MacBook-user ~ % python3.11 -m pip install --upgrade pip
Collecting pip
  Using cached pip-23.0-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
Successfully installed pip-23.0

[notice] A new release of pip available: 22.3.1 -> 23.0
[notice] To update, run: /opt/homebrew/opt/python@3.11/bin/python3.11 -m pip install --upgrade pip

so it kind of shows the message on repeat although it says, it has successfully installed pip.

I have already tried to uninstall and reinstall python, but it does not seem to work either.
(I also seem to have some issue with installing specific packages from time to time, which is why I assume something is off, but neither reinstalling nor upgrading has worked)

As per the comment:

which python3.11 shows /Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 - how can I change my setup so it will work with my previous packages?
opt/homebrew/opt/python3.11 is an alias for /opt/homebrew/Cellar/python@3.11/3.11.1

Update:
since the whole M1 thing seems to be a mess, I un- and reinstalled brew, CommandLine Tools and python

I am running things on python 3.10.9 now, having it freshly installed it still says
[notice] A new release of pip available: 22.3.1 -> 23.0
[notice] To update, run: python3.10 -m pip install --upgrade pip

it now is:
which python3.10
/opt/homebrew/bin/python3.10

(regardless of whether I update like the above python3.10 -m pip install --upgrade pip or pip3 -m pip install --upgrade pip or python3 -m pip install --upgrade pip it will always keep complaining with the note above.

The Python interpreter that runs when you type python in your shell is determined by your PATH - unless you use the alias command, see note at bottom about why I suggest you do not use that.

Paths with the word "local" or "homebrew" in them are generally items installed by homebrew.

Paths starting with /Library or containing Frameworks are generally items supplied by Apple and should not be removed.

You appear to be running an Apple-supplied Python, so your PATH is wrong. If you want to run the homebrew Python, you need to run:

brew info Python

and read and do exactly what it says in respect of versioned links, unversioned links and your PATH.

Note that Python and pip versions are inextricably linked. You must run the pip that matches your Python or you will go around in circles updating the wrong one.

You can see which Python you'll run when entering python in your shell by running:

type python

Likewise, you can see which pip you'll start by running:

type pip

You can see which Python you are running from inside a script or inside an IDE, and also where it is looking for packages:

import sys
# Where is the Python I am running?
print(sys.executable)
# Where is it looking for packages?
print(sys.path)

# Where did it find Numpy, or any other package?
import numpy as np
print(np.__file__)

You can see where pip installed a package, say flask with:

pip show flask

Note: It is possible to define an "alias" like this:

alias python=/some/path/to/some/python

IMHO, that is a bad idea as aliases are not respected in:

• cron jobs, so you'll get problems as soon as you try to run a Python process on a schedule
• Python subprocesses, so you'll get problems as soon as you call suborocess.run(...)
• IDEs, so you'll get problems when you use PyCharm, VS Code and so on.

Also, if you alias python to some version 3.10 but don't alias pip to the same version, you will get in a mess.

Note: homebrew installs its packages in its "Cellar" and then makes symbolic links (symlinks) to them from /usr/local/bin or /opt/homebrew/bin. In general, you should use the latter rather than directly using the binaries in the Cellar because then:

• homebrew can manage the links to allow you to switch versions simply
• you'll only need one PATH to allow you to use all homebrew packages