I don't remember where I read (here around probably) that having a "client pluggable" syntax was not good for python because then ,and more blah blah.I believed it was a rule of the thumb.. But ,when a client programmer like me writes code he tries to give a clean, unambigous interface/syntax for a possible under user.Having a fixed set of keywords and not overridable syntactic sugar is just a limit.Once a sound set of unittest is written with documentation, every useful library would add its keywords. What I start thinking reading here is that if you let redefine, instead: 1) print statement :I will redefine it like now , no matter if python 3.0 is not selling it any more in the language 2) on A take B or C: How ever and whatever one would like to write, this expression could be definable, ending all the pathetic blah blah (hope not to offend) Thanks for jour job anyway. Paolino
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