Looks like #Python Poetry 2.0 got released today.
Lots of fixes, changes & other goodies.
Time to update the projects.
https://python-poetry.org/blog/announcing-poetry-2.0.0/
=> More informations about this toot | More toots from kevinbowen@fosstodon.org
Well that's not too bad, I guess. All of my project tests still pass with Poetry 2.0. Nothing appears broken so far.🎉
There's going to be a bit of cleanup to the pyproject.toml; but, that's to be expected. I've already previously deprecated the use of ^(caret) for versioning constraints. So I don't have to deal with that now.
The output from poetry check
gives me my new homework assignment:
[#]Python
=> More informations about this toot | More toots from kevinbowen@fosstodon.org
Using Poetry's own pyproject.toml https://github.com/python-poetry/poetry/blob/main/pyproject.toml as a reference and the occasional glance at the docs made the conversion to 2.0 compatibility pretty straightforward.
[#]Python
=> More informations about this toot | More toots from kevinbowen@fosstodon.org
Also, for #CI tasks, you've got to add a line to install poetry-plugin-export
since that is no longer included in Poetry core(e.g. if you are exporting into a requirements.txt to create a venv for testing).
A shell has also been move out of core, you'll need poetry-plugin-shell
.
[#]Python
=> More informations about this toot | More toots from kevinbowen@fosstodon.org
text/gemini
This content has been proxied by September (3851b).