Is there a way to create an environment with the dependencies installed but not the project itself without relisting the dependencies?

[schuelermine]

If I set skip-install = true, neither the project nor its dependencies are installed.
If I want to install the project’s dependencies I have to list them again, right?
Is there an easy way I can have an environment with the project’s dependencies but not the project itself installed?

[ofek]

Not yet, but you can use project.optional-dependencies without installation as the environment features option

[dschneiderch]

can you elaborate on this?

[dschneiderch]

i was expecting alembic to be constrained to 1.13.2 when i create the dev env

name = "intent-composer"
description = "Add your description here"
readme = "README.rst"
requires-python = "~=3.11"
dynamic = ["0.0.1"]
dependencies = ["bombora-composer3-airflow2==0.1.3"]

[tool.hatch.envs.dev]
skip-install = true
python = "3.11"
dependencies = [
    "apache-airflow[kubernetes,google,amazon,ftp,ssh]==2.9.1",
    "bombora-composer3-airflow2==0.1.3",
    "ruff~=0.6",
]

[project.optional-dependencies]
dev = [
    "absl-py==2.1.0",
    "agate==1.9.1",
    "aiodebug==2.3.0",
    "aiofiles==23.2.1",
    "aiohttp==3.9.5",
    "aiosignal==1.3.1",
    "alembic==1.13.2"
]

[ofek]

https://hatch.pypa.io/latest/config/environment/overview/#features

[dschneiderch]

Is there any way to provide constraints ?

[schuelermine]

I don’t understand why the currently available options are as they are. It seems to me that it would be much more useful to have an environment that did not have the project installed, so I don’t understand why that’s not the default. I can only really think of one use for having the project installed in an environment: testing. Is there some other reason I’m missing?

[ofek]

That's an accurate assessment, and testing one's code is the most common situation.

[schuelermine]

Ok, thanks, makes sense.