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
A deprecation warning appears when using the latest version of Poetry (2.0.1) with the following message:
D:\Development\test-project-ml> poetry install --no-rootThe "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.Creating virtualenv test-project-ml-IJSV8PYK-py3.13 in D:\Development\.poetry\cache\virtualenvs...
However, I found it way more clear to just use [tools.poetry. ...] for all dependency groups and poetry also doesn't activly advise against doing so, so maybe no need to change it in the template.
Also, I suggest adding multirun into .gitignore to prevent pushes of hydra logs when using the multirun (-m) option.
The text was updated successfully, but these errors were encountered:
Related, in your article about this template, you use the command poetry shell, which by now is not bundled with poetry anymore, but instead is an own plugin which as to be installed beforehand.
Could be worth adding that step to make, as an optional step in the cookiecutter interactive config phase or giving a hit somewhere.
Ronimsenn
changed the title
[tools.poetry.dev-dependencies] is deprecated / add hydra multirun log directory to .gitignore
[tools.poetry.dev-dependencies] is deprecated / add hydra multirun log directory to .gitignore / poetry shell not bundled with poetry >=2.0.0 anymore.
Jan 15, 2025
A deprecation warning appears when using the latest version of Poetry (2.0.1) with the following message:
Replacing
[tools.poetry.dev-dependencies]
with[tools.poetry.group.dev.dependencies]
works just fine.On that note, Poetry advises to use the
project
property instead for normal dependencies, as it is PEP 508 complient:However, I found it way more clear to just use
[tools.poetry. ...]
for all dependency groups and poetry also doesn't activly advise against doing so, so maybe no need to change it in the template.Also, I suggest adding
multirun
into .gitignore to prevent pushes of hydra logs when using the multirun (-m
) option.The text was updated successfully, but these errors were encountered: