chore: make sure there are project.dependencies in pyproject #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started looking more closely into
pyproject.toml
to see what still needs to be done before release. Consider this WIP but also feel free to cherry-pick. I don't know myself how far should this PR take us. See commits for details.Some loose ends:
requirements.devel
- either add asproject.optional-dependencies
or decide thathatch run
is enough for all devel tasksexclude
for build? Currently, the sdist includes e.g..appveyor.yml
and.github
- which does not matter much, but is a couple of bytes nevertheless.tool.hatch.envs
useextra-dependencies
instead ofdepoendencies
, but onlytool.hatch.envs.tests
has atemplate
defined, and there is nodefault
; it seems to work and datalad-next does it in the same way, but is there a reason to only define extra-dependencies and not dependencies? I understood that extra- is mostly for inheritance.Ping #73
Reference: https://hatch.pypa.io/1.13/config/metadata/