If an exception is thrown while the `asyncio` event loop is running, the
stack trace is pretty complicated. Here's an example:
Traceback (most recent call last):
File "sample_client.py", line 616, in
loop.run_until_complete(main_task)
File "/usr/lib/python3.6/asyncio/base_
AFAIK Python never hides stdlib codelines in tracebacks.
Why we should start to do it in asyncio?
On Tue, Nov 14, 2017 at 4:54 PM Mark E. Haase wrote:
> If an exception is thrown while the `asyncio` event loop is running, the
> stack trace is pretty complicated. Here's an example:
>
> Traceb
I'm not asking to change Python's default behavior. I'm asking if anybody
else likes this idea, has ideas to make it better, and would use it if I
published some form of it on PyPI.
On Tue, Nov 14, 2017 at 10:08 AM, Andrew Svetlov
wrote:
> AFAIK Python never hides stdlib codelines in tracebacks.
Got you.
PyPI library makes sense.
On Tue, Nov 14, 2017 at 5:27 PM Mark E. Haase wrote:
> I'm not asking to change Python's default behavior. I'm asking if anybody
> else likes this idea, has ideas to make it better, and would use it if I
> published some form of it on PyPI.
>
> On Tue, Nov 14,
On Tue, Nov 14, 2017 at 9:54 AM, Mark E. Haase wrote:
...
> print('Async Traceback (most recent call last):')
> for frame in traceback.extract_tb(tb):
> head, tail = os.path.split(frame.filename)
> if (head.endswith('asyncio') or tail == 'traceback.py') and
On Tue, Nov 14, 2017 at 2:00 PM, Roger Pate wrote:
> On Tue, Nov 14, 2017 at 9:54 AM, Mark E. Haase wrote:
> ...
>> print('Async Traceback (most recent call last):')
>> for frame in traceback.extract_tb(tb):
>> head, tail = os.path.split(frame.filename)
>>
On Tue, Nov 14, 2017 at 6:54 AM, Mark E. Haase wrote:
> If an exception is thrown while the `asyncio` event loop is running, the
> stack trace is pretty complicated. Here's an example:
>
[...]
>
> I'm posting here to get constructive criticism on the concept and would also
> like to hear if Curio
