Converge on a single build system/specification

[banesullivan]

We seem to have some duplicate build specs between Hatch and the standard project spec

For example, we have two definitions of development dependencies:

with the standard build tools

pyosMeta/pyproject.toml

Lines 39 to 47 in bcb76bd

	[project.optional-dependencies]
	dev = [
	"black",
	"flake8",
	"pre-commit",
	"pytest",
	"pytest-cov",
	"pytest-mock",
	]

and with hatch

pyosMeta/pyproject.toml

Lines 74 to 75 in bcb76bd

	[tool.hatch.envs.test]
	dependencies = ["pytest", "pytest-cov", "coverage[toml]", "pytest-mock"]

This means that if we add a new test dependency it has to be added in two places (which took me a bit to figure out in #301). Perhaps we're doing this wrong and that hatch section should point to the already defined dev dependencies?

I'm not familiar with Hatch or what it provides but it feels a bit redundant here. I'm not against going with Hatch here, I just think we ought to converge on a single spec to prevent needing to update dependencies or scripts in multiple places... perhaps someone more familiar with Hatch can help me correct this?

[lwasser]

Oh, @banesullivan, I'm sorry it's taken me so long to respond. I just actually cleaned this up in our template as well.
Yesterday, Hatch merged a pr that supports dependency-groups, which means that we can put all of the tests and lint, etc, groups there and then add those deps as either features or dependency groups to the environments.

pypa/hatch#1922

So when they make their next release, we can actually clean this up properly.
For the time being, I suggest that we create groups in optional.dependencies which isn't perfect but we can add them to each hatch environment as a feature like we do here:

https://github.com/pyOpenSci/pyos-package-template/blob/main/template/pyproject.toml.jinja#L279

Then, when that hatch release happens, we can add the proper entry to the development-groups table and update the feature to the key that Hatch uses for dev groups (which is different from optional dependencies).

I hope that helps. this should be a really nice, clean update and we can do it in two steps assuming hatch might wait for a release (i don't know what they release schedule is - they just got someone new on their team).