Jason R. Coombs

Thanks for the proposal! I'm open to these improvements, especially where the value exceeds the drawbacks. Here's what I recommend: - Perform independent changes in separate commits. This way, we...

As I'm looking through the links, I'm finding launchpad to be unusable. Some requests take many tens of seconds, others fail with 503 Service Unavailable. As a result, I've been...

I'm no longer confident that we want twine to retain the current behavior (fail if the metadata version is not yet recognized). Since pkginfo was asked to be lenient, perhaps...

This change will incidentally fix #4483, as now packaging becomes a proper dependency instead of an implicit/hidden one.

Thanks for the feedback. I'm not yet sure how I'm going to proceed with this, but given that the tests aren't yet passing, I'm converting this to a draft.

Relevant is [this comment](https://github.com/pypa/twine/issues/1070#issuecomment-2192292401) about supporting `pkg_info>=1.11`, which seems to address this issue.

Twine is [pinned against pkg_info 1.11](https://github.com/pypa/twine/blob/ae71822a3cb0478d0f6a0cccb65d6f8e6275ece5/pyproject.toml#L43-L44), so is hard-blocked against supporting this new metadata version. https://github.com/pypa/twine/pull/1123 proposes to unblock it, but that PR has languished.

@indygreg How do you feel about handing over the keys to `python-zstandard`? Just ownership in PyPI would be enough, or you could also optionally transfer the repo to the coherent-oss...

If someone is interested in doing this work, I'd like to sponsor it (bounty). If you're interested, let's discuss.

Thanks for the report. Happy to explore the issue here. I'm not at all confident that equality by name is correct, because it's possible for multiple distributions of the same...