That flag only prevents the installer from running ensurepip.
Build the python311 package and you will see pip is not included. Edit the PKGBUILD to remove that switch then rebuild and you will see that pip is included.
]]>The OP should post on the python311 AUR page to ask if the `--without-ensurepip` can be removed in the PKGBUILD. I seems to me that should be removed so pip is then available, although I am not an expert.
That flag only prevents the installer from running ensurepip; it should still be available to bootstrap pip manually (but care may be needed to prevent conflicts; I don't know the details): https://docs.python.org/3/library/ensurepip.html
]]>Pip is not included in the python package but has its own package
The python-pip package is built for current Arch python 3.10 so is not relevant here. The OP's question amounts to "why is pip not included in the AUR package python3.11?". The OP should post on the python311 AUR page to ask if the `--without-ensurepip` can be removed in the PKGBUILD. I seems to me that should be removed so pip is then available, although I am not an expert.
I personally never use those AUR packages and prefer to simply use `pyenv install 3.11` which installs to `~/.pyenv/versions/`. I note pyenv does include pip for each built version.
]]>yay -S python311
I assumed this would install a pip paired to the 3.11 executable as well. Yet when I type python3.11 -m pip I get unrecognized command. Is this expected behavior?
Perhaps I misunderstand the relationship between python and pip. I assumed that every python python executable on a system had it's corresponding pip, with pip on it's own pointing to your default python, and python3.x -m pip explicitly invoking the pip paired with python3.x. Is this not correct?
]]>