Using existing conda environment? and Poetry-like behavior for dev deps

[indigoviolet]

I like to set up my environment and install Python with conda. I'd then like to use Hatch for managing dependencies and building etc.

To achieve this, I did

[tool.hatch.envs.default]
path = ".venv"

This has a few issues:

1. There is no command to install dependencies
2. hatch shell does sync dependencies, but also tries to activate the venv (which I don't need to do within Hatch, since I'm already in the conda environment).
3. hatch-conda also tries to take over environment creation and only supports --name environments, meaning that I can't use --prefix environments
4. With poetry, I can mark some dependencies as dev dependencies, and they will install into the same virtual environment. With hatch, that seems impossible, since each environment wants to have its own location. Can I achieve a similar behavior like Poetry for dev dependencies?

[ofek]

With poetry, I can mark some dependencies as dev dependencies, and they will install into the same virtual environment. With hatch, that seems impossible, since each environment wants to have its own location. Can I achieve a similar behavior like Poetry for dev dependencies?

#662 (comment)