[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Change by Serhiy Storchaka : -- pull_requests: -970 ___ Python tracker ___ ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Changes by Donald Stufft : -- pull_requests: +970 ___ Python tracker ___ ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Roundup Robot added the comment: New changeset 7a996e826f83 by Yury Selivanov in branch '3.6': Issue #26182: Fix ia refleak in code that raises DeprecationWarning. https://hg.python.org/cpython/rev/7a996e826f83 New changeset 7b0e79e7f567 by Yury Selivanov in branch 'default': Merge 3.6 (issue

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Brett Cannon added the comment: Sorry I didn't get around to reviewing; I'm sick. On Thu, Sep 15, 2016, 09:51 Yury Selivanov wrote: > > Yury Selivanov added the comment: > > Merged. > > -- > resolution: -> fixed > stage: needs patch -> resolved > status: open

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Yury Selivanov added the comment: Merged. -- resolution: -> fixed stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Roundup Robot added the comment: New changeset 82e6017dc841 by Yury Selivanov in branch '3.6': Issue #26182: Raise DeprecationWarning for improper use of async/await keywords https://hg.python.org/cpython/rev/82e6017dc841 New changeset 3f8b75173543 by Yury Selivanov in branch 'default': Merge

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Yury Selivanov added the comment: I'm going to commit the patch now (I'm going on vacation tomorrow, and I want to watch the buildbots). -- ___ Python tracker

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Yury Selivanov added the comment: I had to rewrite the patch to make sure it reports correct position and covers all cases where using async/await should trigger a warning. Brett, could you please take a look at the patch? -- Added file:

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Brett Cannon added the comment: I'm fine with it being in b2 because IMO the warning really should make it in 3.6 and for stuff like this it's more critical to hit the RC for people's testing than the beta to work out semantic changes. -- ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Ned Deily added the comment: As long as Brett is also OK with it, it can go in for 360b2. -- ___ Python tracker ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Yury Selivanov added the comment: Ned, would it be OK to commit this patch after b1? async/await are scheduled to become real keywords in 3.7. Right now they are only keywords in 'async def' blocks, meaning that it's OK to have a class with 'async' or 'await' attributes. So this will be a

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Changes by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Brett Cannon added the comment: Because parsing is done before execution you can't flip on warnings during runtime in the file you to be affected. As for the line number, that's because it's raise in C code that doesn't have a trigger in Python code. Try importing the code and you should get

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Marco Buttu added the comment: I added the PyErr_WarnEx(PyExc_DeprecationWarning, ...) in Python/ast.c, right below the check for None, True and False as names. Running the following test the message is properly printed: def test_async(self): with self.assertWarnsRegex(DeprecationWarning,

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Brett Cannon added the comment: You need to temporarily turn on warnings for it to work. For example: with warnings.catch_warnings(): warnings.simplefilter('always') with self.assertWarnsRegex(DeprecationWarning, "reserved keyword"): exec('async = 33') Do notice I used

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Changes by STINNER Victor : -- nosy: -haypo ___ Python tracker ___ ___

[issue26182] Deprecation warnings for the future async and await keywords in Python 3.6

Changes by Brett Cannon : -- title: Deprecation warnings for the future async and await keywords -> Deprecation warnings for the future async and await keywords in Python 3.6 ___ Python tracker