RetroSearch Browse

Mon Apr 27 00:16:26 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-April/139554.html

Brett,

On 2015-04-26 6:09 PM, Brett Cannon wrote:
>   How is it a burden for people porting Python 2 code? Because they won't
> get to name anything 'async' just like anyone supporting older Python 3
> versions? Otherwise I don't see how it is of any consequence to people
> maintaining 2/3 code as it will just be another thing they can't use until
> they drop Python 2 support.

Agree.  Also, the PEP states that we'll either keep a modified
tokenizer or use __future__ imports till at least 3.7.  It's
*3 or more years*.  And if necessary, we can wait till 3.8
(python 2 won't be supported at that point).

Thanks!
Yury

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-April/139554.html below:

[Python-Dev] PEP 492: No new syntax is required