Migrate pyproject.toml to PEP 621 / Poetry 2.0

[dalito]

The dynamic versioning plugin that is used here may not be fully Poetry-2.0-ready. It fails with a PEP 621 style config.

Poetry 2.0 also does still not support recursive extra dependencies: They just closed the bug report instead of solving it 😕 python-poetry/poetry#3369 - So this feature cannot be used atm.

Poetry 2.0 also has problems while resolving dependencies:

(.venv) λ poetry lock --regenerate
Updating dependencies
Resolving dependencies... (0.5s)

The current project's supported Python range (>=3.9) is not compatible with some of the required packages Python requirement:
  - linkml-runtime requires Python <4.0,>=3.8, so it will not be satisfied for Python >=4.0
  - linkml-runtime requires Python <4.0,>=3.8, so it will not be satisfied for Python >=4.0
  - linkml-runtime requires Python <4.0,>=3.8, so it will not be satisfied for Python >=4.0
  - linkml-runtime requires Python <4.0,>=3.8, so it will not be satisfied for Python >=4.0

Solution: https://python-poetry.org/docs/main/pyproject#requires-python

[markdoerr]

Hi @dalito,
over the holidays I collected some experience with uv - and it is very very impressive, what it does and at which speed. I am currently migrating all LARA repos to uv to save a lot of CI time.
It could also be considered in this project.

Here are some helpful how-tos:

https://github.com/astral-sh/setup-uv

https://hynek.me/articles/ditch-codecov-python/

[dalito]

I normally do not use poetry if I have the free choice. Here we inherited it from the linkml cookiecutter template. I prefer pip with hatch, pipx & piptools or now uv which is a really great alternative.

Switching to another tool is now easier due to the PEP 621 compliance. :-)