Hello, > "Is anyone truly attached to nested tuple function parameters; 'def > fxn((a,b)): print a,b'? /.../ > > Would anyone really throw a huge fit if they went away? I am willing > to write a PEP for their removal in 2.6 with a deprecation in 2.5 if > people are up for it." First I missed the def and thought "Oh no don't remove it sometimes I pass a tuple to my functions". But the I saw the "def" keyword and realized I never used such a function syntax. So, in one line (my mailer truncated it): def fxn((a,b)): print a,b' for removal, not: 'fxn((a,b)' function calls I'm ok with removal. bye by Wolfgang
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