-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
4.1.2 test suite regressions with Python 3.10.0b4: TypeError: isinstance() arg 2 must be a type, a tuple of types or a union #9505
Comments
This is how a similar problem was fixed in hypothesis: https://github.com/HypothesisWorks/hypothesis/pull/3044/files |
Oops... the change of NewType was introduced after b4 release. It will be included in the next release (rc1?). Could you wait for it for a while? |
That would effectively mean we can't package new Sphinx version until it happens. Can't you just extend |
Hi, seems one of our tests is failing on this on Fedora Rawhide.
Sure, but how roughly long is "a while"? :) Is it worth disabling failing tests or will it be fixed soon? |
Hello, I also found the same error when running |
3.10.0rc1 will be released next Monday. IMO, it's not too far. |
Aaah, OK, I see, so sphinx should be compatible with 3.10.0rc1, right? That is wonderful news, thank you very much @tk0miya 👏 |
Yes, we're using the HEAD of 3.10 for testing. So it will be compat with 3.10.0rc1. (But I can't promise that because it's still fragile) |
And so it turns out that due to other last minute changes, sphinx 4.1.2 is compatible neither with 3.10.0b4 nor with 3.10.0rc1. |
Describe the bug
Sphinx 4.1.2's test suite has 367 test failures and 13 errors with Python 3.10.0b4. They all seem to have a common cause in:
How to Reproduce
Expected behavior
No response
Your project
n/a
Screenshots
No response
OS
Gentoo Linux
Python version
3.10.0b4
Sphinx version
4.1.2 (+ git master)
Sphinx extensions
No response
Extra tools
No response
Additional context
Full superverbose build log (17M): dev-python:sphinx-4.1.2:20210727-064745.log
The text was updated successfully, but these errors were encountered: