Samuele Pedroni wrote:
> From: "Guido van Rossum" <guido@python.org>
> > Still, I'm beginning to be more and more against any form of
> > if-then-else; I'm not yet sure why that is, but I think that I don't
> > see enough places where it's needed, and I find code using it often
> > harder to read. Part of that is my general problem with decyphering
> > expressions with control flow -- my brain is wired to deal with
> > control flow at the statement level very efficiently, but not at the
> > expression level.
>
> If the vote pass, you can always add it but declare that it is very very very
> bad style <wink>.
Or better yet, just introduce a fast c-implemented "ifelse" that does it without
short-circuiting. Thus we can stay with "limited" but easily readable
expressions with Python. IIRC nobody on c.l.py has come up with a real need
for short-circuiting with the ternary op, anyway.
Writing simple statements rather than dense expressions seems
like a key feature of Python to me. Although i love oneliners
(look at the aspn-cookbook-site) to explore the language.
Better to think <wink> with </wink> new statements rather
than new expressions chained to an endless series of names.
holger
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