3 ms·
> 3. In Python 2.c, warnings begun being issued when you tried to use the old way, explaining you needed to change or your code would stop working. > 4. In Pyt
by philh 13y ago
> 3. In Python 2.c, warnings begun being issued when you tried to use the old way, explaining you needed to change or your code would stop working.
> 4. In Python 2.d, it actually did stop working.
I'm curious, what are some examples here? The `from __future__`s that I recall offhand are `print_function`, `division` (still need to be explicit) and the old `with_statement` (incompatible code broke as soon as this became default).
The other old way of doing things that I can think of offhand is `catch Exception, e`, which has been replaced with `catch Exception as e`, but not removed.
- sepeth 13y agothere is `unicode_literals` too. For the full list, see http://docs.python.org/2/library/__future__.html http://docs.python.org/2/library/__future__.html And there is one forgotten in that list: from __future__ import braces
- philh 13y agoSo it looks like in Aaron's list, 2.a == 2.c and 2.b == 2.d, and the process has been completed only three times, and two of those times were just adding keywords.