Document poetry2 requirement

[cmungall]

Looks like we got rid of [tool.poetry] for poetry 2.0, but is it expected it fails for poetry 1 now?

The Poetry configuration is invalid:
  - The fields ['authors', 'description', 'name'] are required in package mode.
  - Additional properties are not allowed ('requires-poetry' was unexpected)
  - Additional properties are not allowed ('requires-plugins' was unexpected)

[dalito]

Yes, because poetry 1.x cannot read PEP 621 conform pyproject.toml. Compatibility with both poetry versions would only be possible if this key feature of poetry 2 is not used.

But does poetry 2.0 not work correctly with pyproject.toml for poetry 1.8 files? I have only seen problems for very old files (poetry<1.4).

[cmungall]

OK, so it sounds like the general recommendation is that everyone should upgrade to poetry 2 - would be great to get a note in the README about this.

Tip from @pkalita-lbl:

But you can still use the Poetry 2 CLI with the old pyproject.toml format. The only thing you might notice is that poetry shell is gone — if you were using that. What I’ve settled on for now is having Poetry 2 as my default poetry command:

pipx install poetry

And keeping Poetry 1.x around as poetry1 if I really l need it for some project:

pipx install --suffix=1 'poetry<2.0'