[issue15253] xmlrpclib.ServerProxy does not support 2-tuple value for uri parameter

2012-07-05 Thread Martin v . Löwis
Martin v. Löwis added the comment: The situation is now much different from what it was for #1561. Python 2 is closed for anything but bug fixes; this rules out code cleanup as well. -- ___ Python tracker ___

[issue15253] xmlrpclib.ServerProxy does not support 2-tuple value for uri parameter

2012-07-05 Thread Vincent Pelletier
Vincent Pelletier added the comment: Then I guess SafeTransport should be cleaned to remove its dead code (tuple host handling), and the class you link to should be included (in spirit if not verbatim) in xmlrpclib. Also, sorry, I realized after posting that this bug is a dupe of #1581. But t

[issue15253] xmlrpclib.ServerProxy does not support 2-tuple value for uri parameter

2012-07-05 Thread Martin v . Löwis
Martin v. Löwis added the comment: This is not a bug; the uri parameter is documented as an URI. Your report can be considered as a feature request (for supporting non-URI values for the uri parameter), however, Python 2 is closed for new features, so this could only be added for 3.x. Closin

[issue15253] xmlrpclib.ServerProxy does not support 2-tuple value for uri parameter

2012-07-05 Thread Vincent Pelletier
New submission from Vincent Pelletier : SafeTransport class supports a 2-tuple as uri, in order to pass x509 parameters to httplib.HTTPSConnection . xmlrpclib.ServerProxy.__init__ fails when given such tuple, because it calls: urllib.splittype(uri) without checking uri type first. Minimal tes