4 ms·
Everything about language maintenance isn't "just" adding features. There's actual bug fixes and a bunch of other stuff that take a lot of time. Not to mention
by rtpg 6y ago
Everything about language maintenance isn't "just" adding features. There's actual bug fixes and a bunch of other stuff that take a lot of time. Not to mention that Python's standard library is relatively large.
- roenxi 6y agoAll the evidence is 2 Full Time Developers are equal to the workload. People aren't using Python because it is going to be good enough in the future, it is good enough now. If more people are working on it full time, we'll just get more Walrus Operators. A very hypothetical gain at cost of an increasingly complex core language.
- more-coffee 6y agoI always have been and always will be against the walrus operator. I don't care how much anyone tries me to sell it on its elegance. There's just no _need_. It's already the #1 example of wtfpython https://github.com/satwikkansal/wtfpython#-first-things-first- https://github.com/satwikkansal/wtfpython#-first-things-firs... /rant. Those kind of features are going to keep coming anyway, I'm afraid.
- coldtea 6y agoIt's the #1 example of wtfpython for no good reason. It's like someone used to PHP or JS style coercion, doing: 1 + "2", getting a type error and asking "wtf python?". The walrus operator is obvious, and very handy in many cases. The capture part of the pattern matching PEP, on the other hand, has been designed shodilly.
- Skunkleton 6y agoI don’t like the walrus operator personally, but wtfpython has it wrong. It’s simply syntax for an expression that includes a binding. It parses like any other expression, and is completely unsurprising.