[issue46963] Deep Lazy Imports - Interpreter-level deferred module loading

Change by Zsolt Dollenstein : -- nosy: +zsol ___ Python tracker <https://bugs.python.org/issue46963> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue46290] Parameter names are inaccurate in dataclasses docs

Change by Zsolt Dollenstein : -- keywords: +patch pull_requests: +28655 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30450 ___ Python tracker <https://bugs.python.org/issu

[issue46290] Parameter names are inaccurate in dataclasses docs

New submission from Zsolt Dollenstein : Parameter names for `asdict`, `astuple`, `is_dataclass`, and `replace` are incorrect in the docs. The first parameter for all these is `obj`. -- assignee: docs@python components: Documentation messages: 409957 nosy: docs@python, zsol priority

[issue39613] IsolatedAsyncioTestCase closes default event loop

Change by Zsolt Dollenstein : -- nosy: +zsol ___ Python tracker <https://bugs.python.org/issue39613> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33363] async for statement is not a syntax error in sync context

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- pull_requests: +6315 ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33363> ___

[issue33363] async for statement is not a syntax error in sync context

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- keywords: +patch pull_requests: +6312 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue33363] async for statement is not a syntax error in sync context

New submission from Zsolt Dollenstein <zsol.z...@gmail.com>: Since 3.7, async generators can be used in non-async functions. The way this is implemented allows the following to be valid syntax: def f(): async for i in aiterable: pass return 1 The return value of the

[issue33337] Provide a supported Concrete Syntax Tree implementation in the standard library

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- nosy: +zsol ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue7> ___ _

[issue33349] 2to3 fails to parse async generators in non-async functions

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- keywords: +patch pull_requests: +6288 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue33266] 2to3 doesn't parse all valid string literals

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker <rep...@bugs.python.org> <https://bu

[issue33349] 2to3 fails to parse async generators in non-async functions

New submission from Zsolt Dollenstein <zsol.z...@gmail.com>: This is valid since python3.7: ``` def f(): return (i * 2 async for i in arange(42)) ``` but lib2to3 doesn't parse this properly, because `async` is tokenized as a `NAME` instead of `ASYNC` -- components: 2to3 (2.

[issue33348] lib2to3 doesn't parse f(*[] or [])

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- keywords: +patch pull_requests: +6286 stage: -> patch review ___ Python tracker <rep...@bugs.python.org> <https://bugs.pyt

[issue33348] lib2to3 doesn't parse f(*[] or [])

Change by Zsolt Dollenstein <zsol.z...@gmail.com>: -- components: 2to3 (2.x to 3.x conversion tool) nosy: zsol priority: normal severity: normal status: open title: lib2to3 doesn't parse f(*[] or []) type: behavior ___ Python tracke

[issue33266] 2to3 doesn't parse all valid string literals

New submission from Zsolt Dollenstein <zsol.z...@gmail.com>: For example `rf"blah"` is not tokenized properly. -- components: 2to3 (2.x to 3.x conversion tool) messages: 315215 nosy: Zsolt Dollenstein priority: normal severity: normal status: open title: 2to3 doesn't