Change by Roel van der Goot :
--
components: asyncio
files: show.py
nosy: cannedrag, yselivanov
priority: normal
severity: normal
status: open
title: asyncio.create_subprocess_exec doesn't capture all stdout output
type: behavior
versions: Python 3.6
Added file: https://bugs.pytho
New submission from Roel van der Goot :
$ python3
Python 3.6.3 (default, Oct 3 2017, 21:45:48)
[GCC 7.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> async def arange(n):
... for i in range(n):
...
Roel van der Goot added the comment:
Zachary,
Thank you for your response. I had the impression that async comprehensions are
a bridge between async functions and non-async functions. Is there a wat to use
async (and asyncio) and then go back to regular python? Or am I just wishful
thinking
Roel van der Goot added the comment:
I have been thinking about my previous comment a bit more. For consistency
there should at least be an await somewhere to move back from async land to
non-async land.
For example:
#!/usr/bin/env python3
import asyncio
async def main
Roel van der Goot added the comment:
Thank you!
--
___
Python tracker
<https://bugs.python.org/issue31832>
___
___
Python-bugs-list mailing list
Unsubscribe:
