You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finished creating environment: default
/usr/bin/python: No module named pip
Finished installing project in development mode
I think, there are three issues here:
A) I guess, hatch should break with an error, if pip is unavailable.
B) hatch.env.system does not use the python setting of the environment.
Maybe this is intended? Only the virtual environment is documented at the moment. Thus, it is unclear, whether the python setting should be supported by the system environment, too. I just expected it here.
C) hatch prefers /usr/bin/python over /usr/bin/python3
Here on my Debian system /bin/bin/python is still pointing to Python2. This is a valid setup according to PEP-394.
This issue is related to #583. Maybe not all aspects of that issue were fixed by 90a77ef.
Regarding (C): I would suggest to reverse the order of search paths in env.plugin.interface (system_python).
The text was updated successfully, but these errors were encountered:
Previously hatch used `python` as the default name of the interpreter.
This was not in line with PEP-394 [1], since `python` is still allowed
to point to a Python 2.x interpreter.
PEP-394 recommends to use `python3` in a system context and `python` in
the context of a virtual environment.
This change should not affect existing setups, since `python3` is
expected to exist under all circumstances (according to PEP-394).
The change will relieve users from the burden of adding
`python = /usr/bin/python3` to their environment configuration for hatch
in order to support setups, where a Python 2.x interpreter is
reachable via `python` (as specified in PEP-394).
The other occurrences of `python` within hatch's code seem to be used
within virtual environments (i.e. `python` is suitable here).
See pypa#583
See pypa#1820
[1] https://peps.python.org/pep-0394/
pyproject.toml
file:hatch --verbose env create default
:I think, there are three issues here:
hatch
should break with an error, ifpip
is unavailable.hatch.env.system
does not use thepython
setting of the environment.virtual
environment is documented at the moment. Thus, it is unclear, whether thepython
setting should be supported by thesystem
environment, too. I just expected it here.hatch
prefers/usr/bin/python
over/usr/bin/python3
/bin/bin/python
is still pointing to Python2. This is a valid setup according to PEP-394.This issue is related to #583. Maybe not all aspects of that issue were fixed by 90a77ef.
Regarding (C): I would suggest to reverse the order of search paths in
env.plugin.interface
(system_python
).The text was updated successfully, but these errors were encountered: