[issue7802] socket.gaierror before ProtocolError for xmlrpc.client

Georg Brandl added the comment: Thanks, that example was indeed wrong. ProtocolError is not meant to be raised if the HTTP connection to the specified URI can't even be made, e.g. for unknown hosts. Fixed in r77858. -- resolution: -> fixed status: open -> closed __

[issue7802] socket.gaierror before ProtocolError for xmlrpc.client

Ezio Melotti added the comment: FWIW it had the same behavior already on Python 2.4. -- nosy: +ezio.melotti, loewis priority: -> normal stage: -> test needed ___ Python tracker ___

[issue7802] socket.gaierror before ProtocolError for xmlrpc.client

New submission from Michael Newman : Following the example in Section 20.23.5. ProtocolError Objects of: http://docs.python.org/3.1/library/xmlrpc.client.html It implies that an invalid URL will give raise an xmlrpc.client.ProtocolError. Instead I'm getting a socket.gaierror instead. (I also tri