➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2016-08-01 22:50 by bayandin, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| create_server-multiple-ports.patch | bayandin, 2016-08-01 22:50 | review | ||
| Messages (8) | |||
|---|---|---|---|
| msg271792 - (view) | Author: Alexander Bayandin (bayandin) | Date: 2016-08-01 22:50 | |
Make create_server accept a list of ports to listen. Now it contains only code changes without updates in docs and tests. If these changes will be considered as helpful I'll be glad to add tests and update documentation for the method. |
|||
| msg271793 - (view) | Author: Guido van Rossum (gvanrossum) *  |
Date: 2016-08-01 23:01 | |
IIRC we got a similar PR before. But what's the problem with creating multiple server objects? |
|||
| msg271794 - (view) | Author: Alexander Bayandin (bayandin) | Date: 2016-08-01 23:24 | |
I think it is just handier than creating several server objects like it is already done for a list of hosts. For me in particular, need to have exactly the same logic for multiple ports which generates randomly and I want to have one predefined port for manually checking/debugging. |
|||
| msg271795 - (view) | Author: Alexander Bayandin (bayandin) | Date: 2016-08-01 23:47 | |
Furthermore, there is a problem with overlapped ports for multiple created server objects. Also, I can quote a comment from 'original' issue: http://bugs.python.org/msg237794 |
|||
| msg276625 - (view) | Author: Yury Selivanov (yselivanov) * |
Date: 2016-09-15 21:45 | |
I think this has been already fixed. Please reopen if I missed something. |
|||
| msg277381 - (view) | Author: Alexander Bayandin (bayandin) | Date: 2016-09-25 14:52 | |
Yury, in 3.6 is added support for multiple hosts for create_server but not for multiple ports which I suggest to add. |
|||
| msg308814 - (view) | Author: Andrew Svetlov (asvetlov) * |
Date: 2017-12-20 21:05 | |
Let's don't -- all combinations of hosts, ports, sock objects makes a mess already. I suggest not complicate already complex signature and just close the issue as "won't fix". Multiple server objects never was a problem. |
|||
| msg308826 - (view) | Author: Yury Selivanov (yselivanov) * |
Date: 2017-12-20 21:34 | |
Agree. It's also challenging to design the API that binds to multiple hosts *and* ports -- a crossproduct of some sorts. > Multiple server objects never was a problem. Right. Let's close this. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:34 | admin | set | github: 71852 |
| 2017-12-20 21:34:17 | yselivanov | set | status: open -> closed resolution: rejected messages: + msg308826 |
| 2017-12-20 21:05:28 | asvetlov | set | nosy:
+ asvetlov messages: + msg308814 |
| 2016-09-25 14:52:28 | bayandin | set | status: closed -> open resolution: out of date -> (no value) messages: + msg277381 versions: - Python 3.5 |
| 2016-09-15 21:45:01 | yselivanov | set | status: open -> closed resolution: out of date messages: + msg276625 stage: resolved |
| 2016-08-01 23:47:17 | bayandin | set | messages: + msg271795 |
| 2016-08-01 23:24:45 | bayandin | set | messages: + msg271794 |
| 2016-08-01 23:01:24 | gvanrossum | set | messages: + msg271793 |
| 2016-08-01 22:50:47 | bayandin | create | |