Florian Schulze wrote: > Does it really need to be only one character? Would this make the > parser to complicated? If not, I would propose '::' which stands out > much more than ':' Anything involving colon might break tools who believe that in Python, the colon opens a block. Of course, it might then also be that these tools recognize that there text after the colon (both after the first and after the second one), and assume that this uses the single-line version of suite. > What about '~'? It already is a unary operator: >>> def foo(): ... return 1 ... >>> ~foo() -2 Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4