Re: asyncio does not always show the full traceback

2017-03-03 Thread gst
Le mercredi 1 mars 2017 09:25:48 UTC-5, Frank Millman a écrit : > "Frank Millman" wrote in message news:o93vs2$smi$1...@blaine.gmane.org... SNIP > > If you run this as is, it works. > > I added '1/0' at various points, to force an exception. > > If I put it in main() or in aenum(), I do not

Re: asyncio does not always show the full traceback

2017-03-02 Thread Frank Millman
"INADA Naoki" wrote in message news:caefz+tz8hvwmh5cf17mv3accdqthj1axddga8umnznuuwes...@mail.gmail.com... > For completeness, if I place '1/0' in aenum(), I get exactly the same > traceback as the first one above. > I can't reproduce it too. Did you 3.6.0 this time? Or did you used 3.6b4 aga

Re: asyncio does not always show the full traceback

2017-03-02 Thread INADA Naoki
FYI, you can easily find this changelog of Python 3.6rc1: - bpo-28843: Fix asyncio C Task to handle exceptions __traceback__. See also: https://bugs.python.org/issue28843 On Fri, Mar 3, 2017 at 1:11 AM, INADA Naoki wrote: >> For completeness, if I place '1/0' in aenum(), I get exactly the same

Re: asyncio does not always show the full traceback

2017-03-02 Thread INADA Naoki
> For completeness, if I place '1/0' in aenum(), I get exactly the same > traceback as the first one above. > I can't reproduce it too. Did you 3.6.0 this time? Or did you used 3.6b4 again? Please don't use beta when asking question or reporting bug. -- https://mail.python.org/mailman/listinfo/p

Re: asyncio does not always show the full traceback

2017-03-02 Thread Frank Millman
"Frank Millman" wrote in message news:o994og$84k$1...@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 loop.run_until_complete(main()) File "/usr/local/lib/python3.6/asyncio/base_events.py", lin

Re: asyncio does not always show the full traceback

2017-03-02 Thread Chris Angelico
On Thu, Mar 2, 2017 at 11:55 PM, Frank Millman wrote: > If I place '1/0' in main(), this is the traceback - > > Traceback (most recent call last): > File "test_db1a.py", line 25, in >loop.run_until_complete(main()) > File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in > run

Re: asyncio does not always show the full traceback

2017-03-02 Thread INADA Naoki
Could you use 3.6.0 instead of b4? I added 1/0 at: ... async def main(): 1/0 await aenum() ... then: $ pyenv/versions/3.6.0/bin/python3 -VV Python 3.6.0 (default, Jan 16 2017, 19:41:10) [GCC 6.2.0 20161005] $ pyenv/versions/3.6.0/bin/python3 a.py Traceback (most recent call last): File

Re: asyncio does not always show the full traceback

2017-03-02 Thread Frank Millman
"INADA Naoki" wrote in message news:caefz+tyudwjesyttqzg2_romphmjrxqaga2ulgfqv5qbpii...@mail.gmail.com... I can't reproduce it on Linux. Maybe, it's windows specific bug? import asyncio from itertools import count async def aenumerate(aiterable): counter = count() async for x in aite

Re: asyncio does not always show the full traceback

2017-03-02 Thread INADA Naoki
I can't reproduce it on Linux. Maybe, it's windows specific bug? On Wed, Mar 1, 2017 at 11:25 PM, Frank Millman wrote: > "Frank Millman" wrote in message news:o93vs2$smi$1...@blaine.gmane.org... >> >> >> I use asyncio in my project, so most of my functions start with 'async' >> and > > most of m

Re: asyncio does not always show the full traceback

2017-03-01 Thread Frank Millman
"Frank Millman" wrote in message news:o93vs2$smi$1...@blaine.gmane.org... I use asyncio in my project, so most of my functions start with 'async' and most of my calls are preceded by 'await'. If an exception is raised, I usually get the full traceback, but sometimes I just get something l

Re: asyncio does not always show the full traceback

2017-02-28 Thread dieter
"Frank Millman" writes: > I use asyncio in my project, so most of my functions start with > 'async' and most of my calls are preceded by 'await'. > > If an exception is raised, I usually get the full traceback, but > sometimes I just get something like the following - > > Traceback (most recent ca

Re: asyncio does not always show the full traceback

2017-02-28 Thread Frank Millman
John Ladasky wrote in message news:72209011-db09-4ba2-9c5b-f576a30e2...@googlegroups.com... > Does anyone know what I must change to get the full traceback? Three years ago, I had a similar issue with incomplete tracebacks while using multiprocessing.Pool. The discussion is here: https://g

Re: asyncio does not always show the full traceback

2017-02-28 Thread jladasky
> Does anyone know what I must change to get the full traceback? Three years ago, I had a similar issue with incomplete tracebacks while using multiprocessing.Pool. The discussion is here: https://groups.google.com/forum/#!msg/comp.lang.python/qKTNNt8uKKU/biNyslh19ncJ;context-place=msg/comp.la

asyncio does not always show the full traceback

2017-02-28 Thread Frank Millman
Hi all I use asyncio in my project, so most of my functions start with 'async' and most of my calls are preceded by 'await'. If an exception is raised, I usually get the full traceback, but sometimes I just get something like the following - Traceback (most recent call last): File "C:\User