Project configuration w/o packaging?

[rademacher-p]

Though most of my projects are intended to produce packages, some are really just a collection of scripts that are really not meant to be imported (just ran at CLI). When I use hatch in these cases, even when I don't configure build-system or hatch.build metadata, hatch acts like I'm installing a package (and shows one w/ pip list). Is there a way to avoid this and just preserve all the other Hatch goodness (multiple envs, tests, etc.)? Thanks for the help 🙏 🐣

[ofek]

Can you please provide an example? My assumption is that the default heuristic for whether or not to skip installation is not precise enough: https://github.com/pypa/hatch/blob/hatch-v1.9.1/src/hatch/env/plugin/interface.py#L383

I should therefore, if pyproject.toml exists, check the contents to make sure there is no [build-system] table. Is that correct?

[rademacher-p]

Sure - basics of project layout and pyproject.toml below. After further thought, I honestly don't know if my request is justified. The specification of pyproject.toml seems completely focused on packaging. I just really prefer using hatch over venv for post-install commands, etc. 😄 Perhaps I should look more closely at hatch-requirements-txt...

src/
- script_1.py
- script_2.py
pyproject.toml
...

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
...

[project.optional-dependencies]
dev = [...]

[tool.hatch.envs.default]
python = "3.11"
features = ["dev"]
post-install-commands = [...]

[rademacher-p]

Discovered that the skip-install config option achieves most of what I want.