[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue39562] Asynchronous comprehensions don't work in asyncio REPL

Change by Pablo Galindo Salgado : -- pull_requests: -18355 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +18356 stage: -> patch review pull_request: https://github.com/python/cpython/pull/19010 ___ Python tracker __

[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

Pablo Galindo Salgado added the comment: New changeset 90235810ec28ca954bbf4b61a5ae5df7a00db409 by Pablo Galindo in branch 'master': bpo-39965: Correctly raise SyntaxError if await is used outside async functions when PyCF_ALLOW_TOP_LEVEL_AWAIT is set (GH-19010) https://github.com/python/cpy

[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +18358 pull_request: https://github.com/python/cpython/pull/19011 ___ Python tracker _

[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

miss-islington added the comment: New changeset f7e32fcbd65490c921e1836c2399827d14d0eb7b by Miss Islington (bot) in branch '3.8': bpo-39965: Correctly raise SyntaxError if await is used outside async functions when PyCF_ALLOW_TOP_LEVEL_AWAIT is set (GH-19010) https://github.com/python/cpytho

[issue39954] test_subprocess: test_specific_shell() fails on AMD64 FreeBSD Shared 3.x

Kubilay Kocak added the comment: Not suggesting it's the *best* way, but for example, isn't there a way to handle return codes from shell executions such as: https://docs.python.org/3/library/subprocess.html#subprocess.CalledProcessError -- ___ Py

[issue34591] smtplib mixes RFC821 and RFC822 addresses

Daurnimator added the comment: On Sun, 15 Mar 2020 at 08:58, Ashwin Ramaswami wrote: > What do you mean by "it then proceeds to use it as an RFC821 address"? It writes it into an SMTP command as if it was an RFC821 address. This is a problem because not all RFC822 addresses are valid RFC821 a

[issue39965] await is valid in non async functions if PyCF_ALLOW_TOP_LEVEL_AWAIT is set

Yury Selivanov added the comment: Good catch & PR ;) Thanks -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue39966] mock 3.9 bug: Wrapped objects without __bool__ raise exception

New submission from Avram : This bug was introduced with Issue25597 Here's some code that demonstrates the error: import sys from unittest.mock import patch with patch.object(sys, 'stdout', wraps=sys.stdout) as mockstdout: bool(sys.stdout) This works fine in 3.8 and earl

<    1   2