If you are one of the people who doesn't like using whitespace in Python to denote scopes, you can use the C-style {} by importing,from __future__ import braces Output:File "some_file.py", line 1 from __future__
Newlines are just treated like any other whitespace. There’s also no fragment specifier7 for “any token”; the closest is tt but that matches a token tree, which is not actually what I want here — I think it would mean the comment has to be valid Rust code, for one thing!
💡 Explanation: ▶ Name resolution ignoring class scope 💡 Explanation ▶ Rounding like a banker * 💡 Explanation: ▶ Needles in a Haystack * 💡 Explanation: ▶ Splitsies * 💡 Explanation: ▶ Wild imports * 💡 Explanation: ▶ All sorted? * 💡 Explanation: ▶ Midnight ...
If you are one of the people who doesn't like using whitespace in Python to denote scopes, you can use the C-style {} by importing,from __future__ import bracesOutput:File "some_file.py", line 1 from __future__ import braces SyntaxError: not a chance...
💡 Explanation: ▶ Name resolution ignoring class scope 💡 Explanation ▶ Rounding like a banker * 💡 Explanation: ▶ Needles in a Haystack * 💡 Explanation: ▶ Splitsies * 💡 Explanation: ▶ Wild imports * 💡 Explanation: ▶ All sorted? * 💡 Explanation: ▶ Midnight ...
If you are one of the people who doesn't like using whitespace in Python to denote scopes, you can use the C-style {} by importing,from __future__ import braces Output:File "some_file.py", line 1 from __future__ import braces SyntaxError: not a chance...