this assignment operator ":= " which was recently added is a typical example.
Do you think it is necessary to bloat python with too many features?
I happily use a subset of Python including a smattering of new features when they add value to the task at hand. This set of features has evolved over time and makes me more productive and allows me to write clean simple code.
If you don't like a new feature just don't use it. There is no rule that says you should use any feature which doesn't help you write great code.
If there are too many features as opposed to "one and only one way to do it" you will end up with a source code that is unintelligible between two developers.
Imagine it has M+N features that are mutually replaceable. The problem arises when you have a very good programmer that writes a complete program using the M features, and when you get programmer b who is also good but hasn't heard of the M features.
The programmers were both named Robert. So we called the approaches "Robjects" and "Bobjects".
'/'.join(['a', 'b'])
I felt it would be sacrilegious to waste money on these extras — just to clean the dinnerware. Why do you think God gave us tounges? She is now living with an applance salesman.
There's things that are weird, but you can just not use those.
I find static typing useful in certain scenarios, for example.
Having the flexibility to employ certain techniques when needed is very handy.