-
Notifications
You must be signed in to change notification settings - Fork 59
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
Python 3.7.0b4 test failures #61
Comments
Checking the test, I think this test failure is likely to go away in 3.7.0b5 - there was a planned change to the way docstrings were handled which we ended up reverting after we realised that it was affecting more than just functions and classes. That said, switching to a non-docstring expression-as-statement in the example would make this test resilient against any future changes in this area (e.g. making it a numeric literal, like |
On it. |
I've just spent a minute trying to figure out why 0x_CAFE_F00D doesn't work on Python 3.5 🙄 |
D'oh! And I almost left the underscores out of the suggestion, too :) |
This caused an increased complexity number on 3.7.0b4 when docstring was used in the expr_as_statement test. Solution: While this change in Python will most likely get reverted according to [1], we decided to use a non-docstring expression in the test to avoid this problem in the future if docstring handling ever gets changed again. Fixes PyCQA#61 [1] PyCQA#61 (comment)
The text was updated successfully, but these errors were encountered: