Replies: 1 comment 2 replies
-
The project should be installed, try explicitly disabling |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The
path
option to the[tool.hatch.envs.dev]
table, withtype = "virtual"
, accepts an "explicit path to the virtual environment." Maybe I am pushing the interpretation to think that allows me to point to a pre-existing virtual environment, althoughhatch
does not complain. However, when I do this, the project does not get installed in the environment. I only get the project's dependencies. Can I use thepath
argument this way AND also have the project installed?Use case: the environment will include a package for which I turn on "PIP_NO_BINARY", and if I create and activate the environment in advance of running
hatch -e dev shell
I can include that package's build dependencies.Beta Was this translation helpful? Give feedback.
All reactions