Message335930
I propose the close the issue as WONTFIX. I don't see how the current behavior is an issue.
I expect a very large traceback just because a server is down/reject connections. I'm not sure that I want that by default.
> ## The problem
> So currently the loop in `socket.create_connection()` ignores all intermediate errors and reports only the last connection failure,
which might be irrelevant. For instance, when both IPv4 & IPv6 networks are supported, usually the last address is a IPv6 address and it frequently fails with an irrelevant error - the actual cause have already been ignored.
It's not so hard to reimplement create_connection(): it's a loop on getaddrinfo(). So you can decide how to deal with errors.
--
I recall that Yury Selivanov, Nathnaniel Smith and Guido van Rossum discussed the idea of "MultiError": an object which contains multiple exceptions, object which would render properly all exceptions when a traceback is displayed. |
|
Date |
User |
Action |
Args |
2019-02-19 11:45:06 | vstinner | set | recipients:
+ vstinner, brett.cannon, yselivanov, ankostis |
2019-02-19 11:45:06 | vstinner | set | messageid: <1550576706.89.0.312171380718.issue29757@roundup.psfhosted.org> |
2019-02-19 11:45:06 | vstinner | link | issue29757 messages |
2019-02-19 11:45:06 | vstinner | create | |
|