Repository navigation
Preparation for updating wheel to 0.46+ - #5163
Conversation
|
@abravalheri You might wanna update the https://github.com/pypa/setuptools/blob/main/pyproject.toml to wheel>=0.46.0? |
|
Thanks @samhith123, that will be a separated PR. This is just the preparation before doing that. |
8f5f2c7 to
fe7a6a0
Compare
|
#5166 has updated vendored wheel to 0.46.3 |
|
Edit: ah! GitHub status finally updated, there's a current issue: https://www.githubstatus.com/ Normally I see this kind of error when there's no runner available (large runner on an org where they're not available, typo'd runner, usage limit, etc.), but that doesn't make sense here with One could try enabling debug logging: https://docs.github.com/en/actions/how-tos/monitor-workflows/enable-debug-logging |


Summary of changes
#5160 shows an unrelated error started happening when the CI picks up the latest version of wheel. In the CI we can see the following:
My understanding is that this test function is in place to ensure the
PKG-INFO/METADATAfiles generated by the latest setuptools are equivalent to theMETADATAfile generated by the now deprecatedwheel.metadatamodule.This test was particularly important during the transition period (when setuptools started to absorb some of the functions in wheel)... but it has been a while now, so we can consider the implementation to be stable. We should be able to remove the problematic test (or at least simplify it a lot) without risking too much.
Closes #5167
Pull Request Checklist
newsfragments/.(See documentation for details)