List the test dependencies in `pyproject.toml`?
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
In Scipp, we list the test dependencies in the pyproject.toml.
Should we do the same for all packages?
This would allow us to do pip install esssans[test] which would give you an env where you can right away run the unit tests?
So for a local editable build you could do pip install -e .[test] (I think?).
This would also mean that we could get the test dependencies in the conda recipe from the pyproject file, as we do for the run dependencies?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the referenced Scipp pyproject.toml test dependencies with the copier template and its generated package files. Determine whether every generated package should expose a test extra and whether the conda recipe can consume it; done means the intended configuration and affected template files are clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100