Michael Urman wrote: > Just to play devil's advocate here, why not to a function call via a > new __setcall__? You still haven't answered the question of what this buys you over just giving your object a suitably named method that does whatever your __setcall__ method would have done. Can you show a realistic use case for this, that demonstrates a clear advantage to having new syntax? -- Greg
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