Issue Kind

Change in current behaviour

Description

See https://github.com/jfly/2024-03-19-poetry-build-deps-issue for details of a saga I went through this week to figure out why poetry recently stopped installing the transitive dependencies of hatchling.

tl;dr: Hatchling now uses metadata version 2.3, and existing installations of poetry may or may not handle metadata version 2.3 well, depending on if they were installed before or after 2024-03-03 (when pkginfo 1.10.0 was released).

Impact

The next 1.8 release of poetry will be guaranteed to handle metadata 2.3 correctly thanks to #9131. However, upgrading to a fixed version of poetry isn't enough, as your poetry cache may already be poisoned with bad information.

In my option, it would be better if poetry just crashed clearly when presented with unrecognized metadata. I believe the current pkginfo api doesn't make this possible to do, but I've asked upstream if this is something they'd be willing to expand their API to support: https://bugs.launchpad.net/pkginfo/+bug/2058697.

Is this something poetry would be interested in handling differently? If so, please chime in on this bug report upstream with pkginfo.

Workarounds

N/A