Deprecation warnings for the future async and await keywords
Marco Buttu
marco.buttu at gmail.com
Fri Jan 22 11:48:25 EST 2016
More information about the Python-list mailing list
Fri Jan 22 11:48:25 EST 2016
- Previous message (by thread): Deprecation warnings for the future async and await keywords
- Next message (by thread): PyDev 4.5.3 Released
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 22/01/2016 16:59, Ian Kelly wrote: > On Fri, Jan 22, 2016 at 4:12 AM, Marco Buttu<marco.buttu at gmail.com> wrote: >> >I enabled the deprecation warnings in Python 3.5.1 and Python 3.6 dev, and I >> >noticed that assigning to async or await does not issue any deprecation >> >warning: >> > >> >$ python -Wd -c "import sys; print(sys.version); async = 33" >> >3.5.1 (default, Jan 21 2016, 19:59:28) >> >[GCC 4.8.4] > They're not reserved words, see > https://www.python.org/dev/peps/pep-0492/#transition-plan Of course not, in fact I wrote "future keywords" in the subject, because they will be keywords in Python 3.7: https://www.python.org/dev/peps/pep-0492/#deprecation-plans -- Marco Buttu
- Previous message (by thread): Deprecation warnings for the future async and await keywords
- Next message (by thread): PyDev 4.5.3 Released
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list