Poetry is giving me a hard time every single time I come to this project. It is not a stable and reliable choice for managing python environments
Last time I made the change in docs generation (a0be37f) I needed to uninstall and reinstall poetry for some reason (not sure what it was but it was just broken)
Now I am trying to rerun poetry install on a commit for which my poetry install was working 3 weeks ago, but now out of the blue I get No module named 'poetry_plugin_export.exporter'
For which I finally figured out I needed to nuke the .poetry folder
It is a pain that poetry is putting so much friction when coming back to this project. And rdflib is the only project for which I use poetry, so whatever happens was not due to side effects from other projects. It just struggles when facing the trial of time
So I would like to propose to move to uv. Pretty much every devs working with python have moved to it for new projects and never looked back, and the fact poetry requires so much care to work is a good motivation to take the time to migrate off of it.
For a long time there was no clear winner in python project/venv management, poetry introduced a few good ideas but the implementation was not reliable. Hatch and others were cool but still relied on pip broken dependency resolution. Since uv came up it's the clear winner, and it's fully PEP compliant (poetry took time to adopt new PEP standards in the past)
One question that stands is which build backend could be used?
While the backend supports a number of options for configuring your project structure, when build scripts or a more flexible project layout are required, consider using the hatchling build backend instead.
I would be happy to help with the migration
Poetry is giving me a hard time every single time I come to this project. It is not a stable and reliable choice for managing python environments
Last time I made the change in docs generation (a0be37f) I needed to uninstall and reinstall poetry for some reason (not sure what it was but it was just broken)
Now I am trying to rerun
poetry installon a commit for which my poetry install was working 3 weeks ago, but now out of the blue I getNo module named 'poetry_plugin_export.exporter'It is a pain that poetry is putting so much friction when coming back to this project. And rdflib is the only project for which I use poetry, so whatever happens was not due to side effects from other projects. It just struggles when facing the trial of time
So I would like to propose to move to
uv. Pretty much every devs working with python have moved to it for new projects and never looked back, and the fact poetry requires so much care to work is a good motivation to take the time to migrate off of it.For a long time there was no clear winner in python project/venv management, poetry introduced a few good ideas but the implementation was not reliable. Hatch and others were cool but still relied on
pipbroken dependency resolution. Sinceuvcame up it's the clear winner, and it's fully PEP compliant (poetry took time to adopt new PEP standards in the past)One question that stands is which build backend could be used?
hatchling: https://hatch.pypa.io/latest/ it's under pypa, and quite mature, it's the one I have been using for years, and it's the one originally recommended byuvuv_build: https://docs.astral.sh/uv/concepts/build-backend/ is quite recent, so might be a bit more limited that hatchling for advanced build,uvthemselves are mentioning this in the build backend docs:I would be happy to help with the migration