Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

dev: use poetry's post 1.2 format for specifying dev dependencies #88

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

Conversation

muxator
Copy link

@muxator muxator commented Sep 13, 2024

From https://python-poetry.org/docs/managing-dependencies/#dependency-groups:

A note about defining a dev dependencies group

The proper way to define a dev dependencies group since Poetry 1.2.0 is the following:

[tool.poetry.group.dev.dependencies]
pytest = "^6.0.0"
pytest-mock = "*"

This group notation is preferred since Poetry 1.2.0 and not usable in earlier versions.

[...]

Poetry will slowly transition away from the dev-dependencies notation which will soon be deprecated, so it’s advised to migrate your existing development dependencies to the new group notation.

From https://python-poetry.org/docs/managing-dependencies/#dependency-groups:

    A note about defining a dev dependencies group

    The proper way to define a dev dependencies group since Poetry 1.2.0 is the
    following:

    [tool.poetry.group.dev.dependencies]
    pytest = "^6.0.0"
    pytest-mock = "*"

    This group notation is preferred since Poetry 1.2.0 and not usable in
    earlier versions.

    [...]

    Poetry will slowly transition away from the dev-dependencies notation which
    will soon be deprecated, so it’s advised to migrate your existing
    development dependencies to the new group notation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant