IMO, this recipe should be just dropped, but sadly, we still have
a few recipes using pip :-(. I consider using pip on recipes a
big NO NO, and I think we should avoid it.
Besides that...
`pip` moves too fast for us to properly keep up, and installing
pip for whatever Python version is as simple as doing:
> python3.xx -m ensurepip --altinstall
> python3.xx -m pip install --upgrade pip
(replace .xx accordingly, of course)
And then users can just update their pip whenever they like.
This silly typo prevented the inclusion of `/bin/{pip,pip3}`
along with `/bin/pip-3.10` (for the default Python version,
it is always nice to provide non-version-suffixed commands).
* pip: update recipe to 22.3.1
Drop support for Python 2.x (removed from pip on version 21.0).
* pip: keep "pip" and "pip3" comands for the default Python version.
While Haiku usually brings Python with it so its license is available
in the merged licenses directory, this isn't declared as a dependency
anywhere and therefore "chance". Since we yet lack a way to declare this
dependency (for lack of a license entity), duplicate the Python license
in the ports requiring it to make them self-contained.
