Skip to content

Use new way of specifying dev dependencies #498

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ivanovmg
Copy link
Contributor

This PR updates pyproject.toml to use new way of defining development dependencies.

As shown in https://python-poetry.org/docs/managing-dependencies/ the new way (starting from Poetry 1.2.0) of defining dev dependencies is by using [tool.poetry.group.dev.dependencies].

According to poetry docs, they recommend migration towards the new group notation.

Checklist

  • I have double checked that there are no unrelated changes in this pull request (old patches, accidental config files, etc)
  • I have created at least one test case for the changes I have made
  • I have updated the documentation for the changes I have made
  • I have added my changes to the CHANGELOG.md

Related PRs

Precursor for PR #497

This PR updates `pyproject.toml` to use new way of defining
development dependencies.

As shown in https://python-poetry.org/docs/managing-dependencies/
the new way (starting from Poetry 1.2.0) of defining
dev dependencies is by using `[tool.poetry.group.dev.dependencies]`.

According to `poetry` docs, they recommend migration
towards the new `group` notation.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant