-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AttributeError and ModuleNotFoundError after release of 72.x #4518
Comments
And indeed, that attribute was removed. But what is it that's leaving the lingering reference to it? Is it metadata left over from an older Setuptools version? Is it something specific to Brotli? That Brotli package does still declare the I had expected the removal of the |
It's not simply a problem with
|
Indeed, even if I just run |
So I tried re-running the integration tests, and this time, they passed, allowing the release to complete. Looking at the integration tests, I'm struggling to conceive of how such a failure could occur non-deterministically. |
Not sure what happened here but this removal also seems to have broken a bunch of things. I found this issue while debugging an error that came out of nowhere earlier today: Our builds started failing with obscure errors like this while installing our dependencies:
|
For others who have landed here wondering what's going on and how to fix it... Following @jaraco's comment above you might already have a version of
It's temporarily solved it for me. |
Good news is I can replicate the issue with I've yanked 72.0.0 for now while I investigate. |
I'm going to move this discussion to #4519. |
After removing the test command in #4458, the
integration
tests started failing.Several of the tests passed, but one failed:
The traceback, as reported by pip, seems to indicate some issue with an entry point expecting
setuptools.dist.check_test_suite
:The text was updated successfully, but these errors were encountered: