pyptr2 added the comment:
Thanks for looking into this. Some comments:
1.
yuri, I haven't tried the github repo. Is that where the development happens?
The description suggests it is outdated since the adoption, but there are some
commits that aren't in hg...?
Anyhow, the relevant
pyptr2 added the comment:
The test program should try to connect to a bluetooth device, using asyncio.
The bluetooth address is obviously made up, so it would likely fail to do so,
but it should not raise an exception before even trying:
$ python3.5 test_async_btsock.py
Traceback (most recent
Changes by pyptr2 :
--
components: +Library (Lib)
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue27136>
___
___
Python-bugs-list mailin
Changes by pyptr2 :
Added file: http://bugs.python.org/file43028/test_async_btsock.py
___
Python tracker
<http://bugs.python.org/issue27136>
___
___
Python-bugs-list m
pyptr2 added the comment:
s/prevents/causes/
--
___
Python tracker
<http://bugs.python.org/issue27136>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from pyptr2:
Base{Selector,Proactor}EventLoop each have a sock_connect() method, both of
which unconditionally "try" to run base_events' _check_resolved_address() which
is apparently meant to raise an exception when called with an unresolved IP
hostname. (becau
