Codecov Report

Base: 85.33% // Head: 85.38% // Increases project coverage by +0.04% 🎉

Coverage data is based on head (4bfaebd) compared to base (7db1e17).
Patch has no changes to coverable lines.

@@            Coverage Diff             @@
##             main    #1568      +/-   ##
==========================================
+ Coverage   85.33%   85.38%   +0.04%     
==========================================
  Files          91       91              
  Lines        8068     8068              
  Branches     1911     1911              
==========================================
+ Hits         6885     6889       +4     
+ Misses        795      791       -4     
  Partials      388      388              

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Hi there, won't this happen again if packaging releases another version?

Hi there, won't this happen again if packaging releases another version?

so you don't want to pull in any future updates?

i hope you are clear what the issue is here. we only exclude versions that are known to be buggy, removing the old behavior isn't a bug but a feature.

I might not have the full picture of the issue and I'd indeed like future updates. I simply asked to understand if we could face the same issue when, say, packaging 22.1 is released.
If so, the recommendation is to pin packaging in our side in every project?

Honest questions, no intention to debate. Thanks a lot for your support!

@ferminho
There is a discussion about how to have repeatable deployments of pdm over there.: #1558

If so, the recommendation is to pin packaging in our side in every project?

Locally, you probably have a single installation of PDM. In that case you could simply restrict its packaging dependency to exclude the new, unsupported version of packaging, until PDM excludes it itself or becomes compatible with it. This will fix it for all of your local projects.

pipx inject pdm 'packaging!=22.0,!=22.1'

In CI, you'll need to add an instruction to your steps/workflow to restrict it as well, until, again, PDM excludes or supports it.

Locally, you probably have a single installation of PDM. In that case you could simply restrict its packaging dependency to exclude the new, unsupported version of packaging, until PDM excludes it itself or becomes compatible with it. This will fix it for all of your local projects.

We have recently adopted pdm as our standard package manager and we have many installations in Python services, libraries and also environments such as JupyterLab or Databricks. This is why the issue created a bit of havoc everywhere when an old, unused version of pyzqm couldn't be parsed as candidate.

Thanks! moving to the other conversation

This is why the issue created a bit of havoc everywhere when an old, unused version of pyzqm couldn't be parsed as candidate.

If this is what blocks you, it has been already solved by the latest version of unearth, those legacy illegal packages will be skipped.

@frostming can you please make a release with this fix? all my CI pipelines will thank you for it