Python 3.7.0b4 test failures about mccabe HOT 5 CLOSED

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 0x_CAFE_F00D).

from mccabe.

@hroncok @ncoghlan I'd accept a PR that changes the test to using a literal like that for future-proofing purposes. (Although I'm certain whoever wrote this test thought that docstrings were future-proof too 😄 )

from mccabe.

On it.

from mccabe.

I've just spent a minute trying to figure out why 0x_CAFE_F00D doesn't work on Python 3.5 🙄

from mccabe.

D'oh! And I almost left the underscores out of the suggestion, too :)

from mccabe.