You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use of poetry-dynamic-versioning with poetry_pep621 poetry-core@git+https://github.com/radoering/poetry-core.git@pep621-support requires a duplication of the project's name in pyproject.toml.
Pep621 and poetry-core require that the name field is defined as project.name whilst poetry-dynamic-versioning appears to source the project name from tool.poetry.name.
Running poetry_pep621 on a project with a duplicated name field in pyproject.toml returns an error code of 1 due to this duplicated field.
Could poetry-dynamic-versioning extract name from project.name rather than tool.poetry.name when using a pep621 compliant poetry-core build-backend?
The text was updated successfully, but these errors were encountered:
Use of poetry-dynamic-versioning with poetry_pep621
poetry-core@git+https://github.com/radoering/poetry-core.git@pep621-support
requires a duplication of the project's name in pyproject.toml.Pep621 and poetry-core require that the
name
field is defined asproject.name
whilst poetry-dynamic-versioning appears to source the project name fromtool.poetry.name
.Running
poetry_pep621
on a project with a duplicatedname
field in pyproject.toml returns an error code of 1 due to this duplicated field.Could poetry-dynamic-versioning extract name from
project.name
rather thantool.poetry.name
when using a pep621 compliant poetry-core build-backend?The text was updated successfully, but these errors were encountered: