asyncio does not always show the full traceback

Thu Mar 2 08:08:22 EST 2017

"Frank Millman" wrote in message news:o994og84ドルk$1 at blaine.gmane.org...
>> If I place '1/0' in main(), this is the traceback -
>> Traceback (most recent call last):
> File "test_db1a.py", line 25, in <module>
> loop.run_until_complete(main())
> File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in 
> run_until_complete
> return future.result()
> ZeroDivisionError: division by zero
>> If I place '1/0' in gen(), this is the traceback -
>> Traceback (most recent call last):
> File "test_db1a.py", line 25, in <module>
> loop.run_until_complete(main())
> File "/usr/local/lib/python3.6/asyncio\base_events.py", line 466, in 
> run_until_complete
> return future.result()
> File "test_db1a.py", line 17, in aenum
> async for a, x in aenumerate(g):
> File "test_db1a.py", line 6, in aenumerate
> async for x in aiterable:
> File "test_db1a.py", line 11, in gen
> 1/0
> ZeroDivisionError: division by zero

For completeness, if I place '1/0' in aenum(), I get exactly the same 
traceback as the first one above.
Frank