Warning: The file chosen for install of matplotlib 3.9.1 (matplotlib-3.9.1.tar.gz) is yanked. Reason for being yanked: The Windows wheels, under some conditions, caused segfaults in unrelated user code. Due to this we deleted the Windows wheels to prevent these segfaults, however this caused greater disruption as pip then began to try (and fail) to build 3.9.1 from the sdist on Windows which impacted far more users. Yanking the whole release is the only tool available to eliminate these failures without changes to on the user side. The sdist, OSX wheel, and manylinux wheels are all functional and there are no critical bugs in the release. Downstream packagers should not yank their builds of Matplotlib 3.9.1. See https://github.com/matplotlib/matplotlib/issues/28551 for details.
since nomenclature does not feature matplotlib as an explicit dependency, I believe this to be a pyam issue.
As found here https://github.com/IAMconsortium/nomenclature/actions/runs/10248178276/job/28348892224:
Warning: The file chosen for install of matplotlib 3.9.1 (matplotlib-3.9.1.tar.gz) is yanked. Reason for being yanked: The Windows wheels, under some conditions, caused segfaults in unrelated user code. Due to this we deleted the Windows wheels to prevent these segfaults, however this caused greater disruption as pip then began to try (and fail) to build 3.9.1 from the sdist on Windows which impacted far more users. Yanking the whole release is the only tool available to eliminate these failures without changes to on the user side. The sdist, OSX wheel, and manylinux wheels are all functional and there are no critical bugs in the release. Downstream packagers should not yank their builds of Matplotlib 3.9.1. See https://github.com/matplotlib/matplotlib/issues/28551 for details.since nomenclature does not feature matplotlib as an explicit dependency, I believe this to be a pyam issue.