2 ms·
Believe the Python3 change is a bit of a red-herring, everyone learned from that. The breaking point was PEP 572 (ie :=) which was quite controversial. The le
by mixmastamyk 8y ago
Believe the Python3 change is a bit of a red-herring, everyone learned from that.
The breaking point was PEP 572 (ie :=) which was quite controversial. The lesson here: One shouldn't attempt to reverse 25-year old design decisions, not even GvR. Python is too big now.
There was a compromise (and more congruent) alternative, reuse of the "as" keyword, that was thrown out immediately, and proponents rammed 572 thru despite significant objection. That's when things got ugly. Personally I disagreed with that decision, and tried to support the compromise design.
In the end, didn't think 572 was the end of the world (will be occasionally useful, if ugly), and tried to stay polite, but sadly many didn't. Then he accepted 572 and stepped down, as if one last poke in the eye, unfortunately.
- metalliqaz 8y agoI think you're right about 572, although even that wouldn't have been enough without all the other stuff from the past, such as the unicode strings. I often have to write things like this: m = re.match() if m: do something So I'm looking forward to the feature. I'm not sure you were fair to the process about the alternative syntax, though. They did give a well-reasoned explanation for discounting it.
- mixmastamyk 8y agoIt was discounted because it was less flexible, didn't handle as many use cases. True. However, during the process Victor Stinner rewrote one large module using the new syntax as an exercise. We learned that ~95% of the time, only the simplest case was used, the form you gave above. The extra flexibility turned out not very important in real code. We had a choice of ":=" syntax, duplicate but full functionality, and losing the BDFL, or ~95% functionality, language congruity, and keeping him. They chose the former. Maybe Guido stepping aside will be good in the long run however, it was bound to happen eventually.