What's Coming in Python 3.8
lwn.net
What's Coming in Python 3.8
1–10 of 558 posts
Re: What's Coming in Python 3.8
#2Why elif en not juste elseif?
Re: What's Coming in Python 3.8
#3Why elif en not juste elseif?
Or just else if... but honestly elif is easiest to type and it's not hard to understand.
Re: What's Coming in Python 3.8
#4smh
Re: What's Coming in Python 3.8
#5Walrus operator looks like a great addition, not too much syntax sugar for a common pattern. Why were folks arguing about it?
Re: What's Coming in Python 3.8
#6Without wanting to ignite a debate about the walrus operator (and having not read any of the arguments), I can guess why there was one. It's not clear to me what it does just from reading it, which was always one of Python's beginner-friendlinesses.
Re: What's Coming in Python 3.8
#7Re: What's Coming in Python 3.8
#8Python looks more and more foreign with each release.
I'm not sure what happened after 3.3 but it seems like the whole philosophy of "pythonic", emphasizing simplicity, readability and "only one straightforward way to do it" is rapidly disappearing.
Re: What's Coming in Python 3.8
#9Why elif en not juste elseif?
Perhaps to align with the final "else" clause, or it was familiar to c programmers due to the c-preprocessor directive https://gcc.gnu.org/onlinedocs/cpp/Elif.html, or they were mindful that every character counts when you want to push 80 character max-line-length style?
To be clear, that's not a new feature in 3.8.
Re: What's Coming in Python 3.8
#10Speaking as someone who has written Python code almost every day for the last 16 years of my life: I'm not happy about this.
Some of this stuff seems to me like it's opening the doors for some antipatterns that I'm consistently frustrated about when working with Perl code (that I didn't write myself). I had always been quite happy about the fact that Python didn't have language features to blur the lines between what's code vs what's string literals and what's a statement vs what's an expression.