[issue27929] asyncio.AbstractEventLoop.sock_connect broken for AF_BLUETOOTH

2016-09-18 Thread Robert Jordens
Robert Jordens added the comment: It is still in cpython master e6e9ddd. import asyncio import socket sock = socket.socket(family=socket.AF_BLUETOOTH, type=socket.SOCK_STREAM, proto=socket.BTPROTO_RFCOMM) sock.setblocking(False) addr = "00:12:34:

[issue27929] asyncio.AbstractEventLoop.sock_connect broken for AF_BLUETOOTH

2016-09-01 Thread Robert Jordens
Robert Jordens added the comment: https://github.com/python/cpython/blob/master/Lib/asyncio/selector_events.py#L394 https://github.com/python/asyncio/blob/master/asyncio/selector_events.py#L394 AF_UNIX is special-cased. Maybe AF_BLUETOOTH and others should use that same special treatment

[issue27929] asyncio.AbstractEventLoop.sock_connect brooken for AF_BLUETOOTH

2016-09-01 Thread Robert Jordens
Changes by Robert Jordens <jord...@gmail.com>: -- components: +asyncio -Argument Clinic nosy: +gvanrossum, haypo, yselivanov ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue27929] asyncio.AbstractEventLoop.sock_connect brooken for AF_BLUETOOTH

2016-09-01 Thread Robert Jordens
Robert Jordens added the comment: The error for inet_pton() is: >>> import socket >>> socket.inet_pton(socket.AF_BLUETOOTH, "00:12:34:56:78:99") Traceback (most recent call last): File "", line 1, in socket.error: [Errno 97] Address family not su

[issue27929] asyncio.AbstractEventLoop.sock_connect brooken for AF_BLUETOOTH

2016-09-01 Thread Robert Jordens
New submission from Robert Jordens: Since 3.5.2 sock_connect() tries to be smart and resolves addresses for you if they fail a socket.inet_pton() check. But inet_pton() only supports AF_INET(6) and does not work for other address families that socket otherwise supports just fine (e.g

[issue26156] Bad name into power operator syntax

2016-05-06 Thread Robert Jordens
Robert Jordens added the comment: Ack to the new patch. It is semantically confusing that the await expression also served as the power base without any await. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue26156] Bad name into power operator syntax

2016-05-05 Thread Robert Jordens
Robert Jordens added the comment: That should have read "... should _not_ be closed." -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.py

[issue26156] Bad name into power operator syntax

2016-05-05 Thread Robert Jordens
Robert Jordens added the comment: The original bug report is (apart from spelling) correct. This is a bug and it should be closed. Please reopen. This patch reverts the erroneous change in: changeset: 96185:548d5704fcb3 user:Yury Selivanov <yseliva...@sprymix.com> date:

[issue21591] exec(a, b, c) not the same as exec a in b, c in nested functions

2014-05-28 Thread Robert Jordens
New submission from Robert Jordens: According to the documentation the exec a in b, c is equivalent to exec(a, b, c). But in the testcase below the tuple form causes a SyntaxError while the statement form works fine. diff -r e770d8c4291c Lib/test/test_compile.py --- a/Lib/test