Diez B. Roggisch wrote: >>meanwhile, over in python-dev land: >> >> "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." > > > I am - I think that feature is sort of an orthogonality which should be > preserved. No doubt its not one of the most important ones - but if I > can write > > a, (b ,c) = 1, (2,3) > > I'd like to write > > def foo(a, (b,c)): > ... > > foo(1, (2,3)) > > too. > > Diez exactly... consistency is the most important thing here. i use this style all the time. i will be very disappointed to find this removed from python. i'm +1 for keeping it. bryan
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