Sebastien Bourdeauducq added the comment:
Thank you!
--
___
Python tracker
<https://bugs.python.org/issue27500>
___
___
Python-bugs-list mailing list
Unsub
Sebastien Bourdeauducq added the comment:
Any chance someone could look into this bug?
--
___
Python tracker
<https://bugs.python.org/issue27500>
___
___
Pytho
New submission from Sebastien Bourdeauducq :
The current behavior causes an exception to be raised when trying to create a
datagram socket and _ipaddr_info returns None (since asyncio then calls
loop.getaddrinfo with SOCK_STREAM and IPPROTO_UDP).
Preserving socket type is made difficult by
Sebastien Bourdeauducq added the comment:
Windows looks fine.
--
___
Python tracker
<https://bugs.python.org/issue33678>
___
___
Python-bugs-list mailin
Sebastien Bourdeauducq added the comment:
This is still a problem with Python 3.5.3 and 3.6.0.
--
___
Python tracker
<http://bugs.python.org/issue27500>
___
___
New submission from Sebastien Bourdeauducq:
The following code fails with "OSError: [WinError 10022] An invalid argument
was supplied".
import asyncio
loop = asyncio.ProactorEventLoop()
asyncio.set_event_loop(loop)
loop.run_until_complete(asyncio.open_connection("::1"
Sebastien Bourdeauducq added the comment:
The first offending commit is this one:
https://github.com/python/cpython/commit/03df54d549173e17e1cf9a767199de32a363aa6b
more specifically "return af, type, proto, '', (host, port)". For IPv6, it
should be "(host, port, flow
New submission from Sebastien Bourdeauducq:
1. Open a listening socket:
$ nc6 -l -p 1066
2. Run the following (tested here on Linux):
import asyncio
async def bug():
reader, writer = await asyncio.open_connection("::1", "1066")
while True:
writer.
Sebastien Bourdeauducq added the comment:
Yes, this patch fixes the problem (in both this example and my real
application). Thanks!
--
___
Python tracker
<http://bugs.python.org/issue25
New submission from Sebastien Bourdeauducq:
https://github.com/python/asyncio/issues/315
New patch attached.
--
components: asyncio
files: asyncio_norebind.diff
keywords: patch
messages: 260108
nosy: gvanrossum, haypo, sebastien.bourdeauducq, yselivanov
priority: normal
severity
Sebastien Bourdeauducq added the comment:
Can someone have a quick look at this please?
--
___
Python tracker
<http://bugs.python.org/issue26338>
___
___
Pytho
New submission from Sebastien Bourdeauducq:
https://github.com/python/asyncio/issues/319
On Windows, asyncio servers sometimes print such log messages when clients
disconnect:
```
ERROR:master:asyncio:Fatal write error on pipe transport
protocol:
transport: <_ProactorSocketTransport fd=
Sebastien Bourdeauducq added the comment:
Your patch seems to miss the ``_fatal_error`` method in ``proactor_events.py``
(which is actually where the bug happens in my application - it's using
``ProactorEventLoop``).
--
___
Python tracker
Sebastien Bourdeauducq added the comment:
Tested it, that works, thanks!
--
___
Python tracker
<http://bugs.python.org/issue26509>
___
___
Python-bugs-list mailin
Sebastien Bourdeauducq added the comment:
Can someone please commit the patch?
--
___
Python tracker
<http://bugs.python.org/issue26509>
___
___
Python-bugs-list m
New submission from Sebastien Bourdeauducq:
The fix of https://bugs.python.org/issue1218234 is a bit zealous. If the module
has not been reloaded, e.g. calling a function will execute code older than
what inspect.getsource returns.
--
components: Library (Lib)
messages: 264538
nosy
Sebastien Bourdeauducq added the comment:
And since the import statement does not touch linecache, there are many other
cases where inspect.getsource and objects can be out of sync.
--
___
Python tracker
<http://bugs.python.org/issue26
Sebastien Bourdeauducq added the comment:
That could work, but I would have to manually resolve and filter the lists of
hostnames so that the program does not attempt to bind the same address twice -
something that is better implemented in create_server, which already does the
hostname
Sebastien Bourdeauducq added the comment:
See attached.
--
keywords: +patch
Added file: http://bugs.python.org/file38428/asyncio_multibind.diff
___
Python tracker
<http://bugs.python.org/issue23
New submission from Sebastien Bourdeauducq:
I would like to be able to bind asyncio TCP servers to an arbitrary list of
hosts, not just either one host or all interfaces.
I propose that the host parameter of create_server and start_server can be a
list of strings that describes each host
20 matches
Mail list logo