Re:PEP 492 – Coroutines with async and await syntax
by actsasbuffoon on Saturday April 18, 2015 @10:15AM
(#9399507)
Making print a statement again would mean you can't print in a lambda. That'll break a bunch of Python 3 code, which puts us right back where we started; people being upset about a new release of Python breaking their code.
Re:PEP 492 – Coroutines with async and await syntax
by alextgordon on Saturday April 18, 2015 @02:42PM
(#9400538)
You don't need to jettison print-as-a-function in order to have print-as-a-statement.
>>> print "hello"
SyntaxError: Missing parentheses in call to 'print'
If it can print a SyntaxError explaining the problem then it can print "hello".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.
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.
For the people that are stuck with Python 2 legacy code, we'd need something else.
Python-future [1] seems to be able to import some Python 2 modules, but I'm not sure how far it goes.
[1] http://python-future.org/translation.html#translation