Re: [python-tulip] No tracebacks when running from run_until_complete

2016-12-16 Thread Yury Selivanov 
Hm. I’m not sure what’s going on here. Please file a bug on bugs.python.org.

Yury
> On Dec 16, 2016, at 1:19 PM, Carlo Pires  wrote:
> 
> Compiling py36 rc1 gave me this error (running tests):
> 
> Fatal Python error: Segmentation fault
> 
> Current thread 0x2afd4622c380 (most recent call first):
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/test_hashlib.py", 
> line 852 in _test_pbkdf2_hmac
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/test_hashlib.py", 
> line 874 in test_pbkdf2_hmac_c
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/case.py", line 
> 601 in run
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/case.py", line 
> 649 in __call__
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/suite.py", 
> line 122 in run
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/suite.py", 
> line 84 in __call__
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/suite.py", 
> line 122 in run
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/suite.py", 
> line 84 in __call__
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/suite.py", 
> line 122 in run
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/unittest/suite.py", 
> line 84 in __call__
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/support/__init__.py", 
> line 1746 in run
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/support/__init__.py", 
> line 1870 in _run_suite
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/support/__init__.py", 
> line 1904 in run_unittest
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/runtest.py", 
> line 164 in test_runner
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/runtest.py", 
> line 165 in runtest_inner
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/runtest.py", 
> line 129 in runtest
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/main.py", 
> line 343 in run_tests_sequential
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/main.py", 
> line 418 in run_tests
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/main.py", 
> line 490 in _main
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/main.py", 
> line 468 in main
>   File 
> "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/libregrtest/main.py", 
> line 532 in main
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/regrtest.py", line 
> 46 in _main
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/test/regrtest.py", line 
> 50 in 
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/runpy.py", line 85 in 
> _run_code
>   File "/home/carlopires/py36comp/Python-3.6.0rc1/Lib/runpy.py", line 193 in 
> _run_module_as_main
> Segmentation fault (core dumped)
> 
> My env is ubuntu 14.04 amd64
> 
> Any hint?
> 
> 2016-12-16 15:47 GMT-02:00 Yury Selivanov :
> Hi,
> 
> Can you try Python 3.6 rc1?  This is likely related to 
> http://bugs.python.org/issue28843
> 
> Yury
> 
> 
> > On Dec 16, 2016, at 12:44 PM, Carlo Pires  wrote:
> >
> > Hi,
> >
> > I'm starting with asyncio and python3.6 (using Python 3.6.0b4).
> >
> > See this snippet:
> >
> > import asyncio
> >
> > async def fa():
> > return 1/0
> >
> > async def fb():
> > return await fa()
> >
> > async def fc():
> > return await fb()
> >
> > async def test():
> > return await fc()
> >
> > asyncio.get_event_loop().run_until_complete(test())
> >
> >
> > When I run it I get:
> >
> > $ python test0.py
> > Traceback (most recent call last):
> >   File "test0.py", line 18, in 
> > asyncio.get_event_loop().run_until_complete(test())
> >   File "/opt/py36/lib/python3.6/asyncio/base_events.py", line 466, in 
> > run_until_complete
> > return future.result()
> > ZeroDivisionError: division by zero
> >
> >
> > Only the exception is printed, the traceback is missing.
> >
> > If I set PYTHONASYNCIODEBUG it doesn't help.
> >
> > Is this the expected behavior? Do I need to manage to get the traceback 
> > from the coroutine passed to run_until_complete ?
> >
> 
> 
> 
> 
> -- 
>   Carlo Pires

Re: [python-tulip] No tracebacks when running from run_until_complete

2016-12-16 Thread Yury Selivanov 
Hi,

Can you try Python 3.6 rc1?  This is likely related to 
http://bugs.python.org/issue28843

Yury


> On Dec 16, 2016, at 12:44 PM, Carlo Pires  wrote:
> 
> Hi,
> 
> I'm starting with asyncio and python3.6 (using Python 3.6.0b4). 
> 
> See this snippet:
> 
> import asyncio
> 
> async def fa():
> return 1/0
> 
> async def fb():
> return await fa()
> 
> async def fc():
> return await fb()
> 
> async def test():
> return await fc()
> 
> asyncio.get_event_loop().run_until_complete(test())
> 
> 
> When I run it I get:
> 
> $ python test0.py 
> Traceback (most recent call last):
>   File "test0.py", line 18, in 
> asyncio.get_event_loop().run_until_complete(test())
>   File "/opt/py36/lib/python3.6/asyncio/base_events.py", line 466, in 
> run_until_complete
> return future.result()
> ZeroDivisionError: division by zero
> 
> 
> Only the exception is printed, the traceback is missing.
> 
> If I set PYTHONASYNCIODEBUG it doesn't help.
> 
> Is this the expected behavior? Do I need to manage to get the traceback from 
> the coroutine passed to run_until_complete ?
>