Re:PEP 492 – Coroutines with async and await syntax
by scrollaway on Saturday April 18, 2015 @06:31PM
(#9401346)
So instead of code breaking explicitly, you'd rather it breaks implicitly?
You're really foolish if you believe that's better. The print keyword isn't what is preventing 3k adoption.
The only snag is that a tuple would be printed slightly differently, but that is harmless.
People should be upset that a new release of Python breaks their code, because the Python developers acted unprofessionally in expecting all python code in existence to be rewritten to suit their aesthetic fetishes.