>> > [decorator] >> > def func(arg, arg): Barry> I don't like it. It already has a meaning (albeit fairly Barry> useless) and it doesn't seem obvious from just looking at it that Barry> the decorator is connected to the following method. It doesn't Barry> taste Pythonic to me. I'm with Barry. It seems magic to me. If I write def f(): "doc" [47] return 3 today, although a bit weird, [47] doesn't affect the following statement in any way. Now the proposal (still, assuming this isn't an elaborate AFJ) on the table means to change the semantics of an unassigned list expression in one special case. I suggest: Special cases aren't special enough to break the rules. though I know someone will follow with Although practicality beats purity. IN this case there are other practical proposals on the table, not the least of which is the status quo. Skip
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