[issue21566] make use of the new default socket.listen() backlog argument

2014-09-24 Thread Yury Selivanov
Yury Selivanov added the comment: Guys, when you update asyncio code, please make sure you sync your changes with its upstream here: https://code.google.com/p/tulip/ to avoid commits like this 5f001ad90373 The goal is to have single source base for 3.4 and 3.5 in cpython repo and for 3.3 in

[issue21566] make use of the new default socket.listen() backlog argument

2014-07-23 Thread Roundup Robot
Roundup Robot added the comment: New changeset f7643c893587 by Charles-François Natali in branch 'default': Issue #21566: Make use of socket.listen() default backlog. http://hg.python.org/cpython/rev/f7643c893587 -- nosy: +python-dev ___ Python

[issue21566] make use of the new default socket.listen() backlog argument

2014-07-23 Thread Charles-François Natali
Charles-François Natali added the comment: Committed, thanks for the reviews (I only updated one call to socket.listen(), inside multiprocessing, the rest is in the test suite). -- resolution: - fixed stage: patch review - resolved status: open - closed

[issue21566] make use of the new default socket.listen() backlog argument

2014-05-23 Thread Charles-François Natali
New submission from Charles-François Natali: Follow-up to issue #21455: we can now update the stdlib to rely on the default socket listen backlog, instead of having a bazillion different values (which range from 1 to 100!). -- components: Library (Lib) files:

[issue21566] make use of the new default socket.listen() backlog argument

2014-05-23 Thread Antoine Pitrou
Antoine Pitrou added the comment: This looks fine to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21566 ___ ___ Python-bugs-list mailing

[issue21566] make use of the new default socket.listen() backlog argument

2014-05-23 Thread STINNER Victor
STINNER Victor added the comment: Maybe we should keep listen(1) in some cases. For socketpair() of asyncio.windows_utils, it makes sense to use sock.listen(1) since we expect exactly one request from one client. The listening socket is closed just after sock.accept(). --

[issue21566] make use of the new default socket.listen() backlog argument

2014-05-23 Thread Charles-François Natali
Charles-François Natali added the comment: Maybe we should keep listen(1) in some cases. For socketpair() of asyncio.windows_utils, it makes sense to use sock.listen(1) since we expect exactly one request from one client. The listening socket is closed just after sock.accept(). Yeah, I