fix: workaround unsupported metadata version 2.4 in pkginfo

[finswimmer]

pkginfo will show a warning if it detects metadata version:

NewMetadataVersion: New metadata version (2.4) higher than latest supported version: parsing as 2.3
  warnings.warn(NewMetadataVersion(self.metadata_version))

I decided to not suppress this message.

Related to #9670 (comment)

[poetry-bot]

The backport to 1.8 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.8 1.8
# Navigate to the new working tree
cd .worktrees/backport-1.8
# Create a new branch
git switch --create backport-9881-to-1.8
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9e2a8bd5ff6de05d9af03fbefce647b673b13352
# Push it to GitHub
git push --set-upstream origin backport-9881-to-1.8
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.8

Then, create a pull request where the base branch is 1.8 and the compare/head branch is backport-9881-to-1.8.

[MichaReiser]

This fix might no longer be required. A new pkginfo version was released just a few minutes ago that adds support for 2.4.

What would be nice in general is if poetry wouldn't fail when seeing a newer minor version and instead just warns about it.

[dimbleby]

poetry wouldn't fail when seeing a newer minor version and instead just warns about it.

that already is the behaviour, since pkginfo 1.11.0

[radoering]

This fix might no longer be required. A new pkginfo version was released just a few minutes ago that adds support for 2.4.

Thanks for the info.

What would be nice in general is if poetry wouldn't fail when seeing a newer minor version and instead just warns about it.

Poetry did not fail before #9203. However, this resulted in #9195, which is worse than failing. It seems like pkginfo handles unknown METADATA versions better now so maybe we can (partially) revert #9203.

[dimbleby]

poetry only fails on unexpected metadata versions in some of the code paths, which I think adds to the general confusion (including my own)

eg so far as I can see the _get_info_from_metadata() path does not care about metadata version.

Probably this is why some people saw a problem and some did not - they either were or were not using pypi / a private repository.

[broodjeaap]

For anyone looking for a quick fix, you can downgrade poetry with:
poetry self update 1.8.2

[dimbleby]

it's upgrading pkginfo that helps, not downgrading poetry

[Buedenbender]

In my case it was resolved by

pip install --upgrade pkginfo
pip install --upgrade poetry
pip install --upgrade pip

Aftwards i was able to successfully install ruff in my poetry env via
poetry add -G dev ruff