The current xmlrpclib can't communicate through a proxy
server.   In particular, the two Transport classes
contained within xmlrpclib use httplib directly and, as
such, do not support the proxy handling as offered by
urllib.

Or so it seems.

I'm in dire need of support for proxies in xmlrpclib
and will be investigating creating a custom Transport
class that uses urllib as opposed to httplib to gain
support for proxies.

Assuming success, I'll post the new transport class
here.   In the interim, I figured I would log a bug in
case anyone else is interested in working on the
problem (or already has a solution :).

b.bum
bbum@mac.com

Logged In: YES 
user_id=103811

As discussed on python-dev and with Fredrick Lundh, I
created an HTTPTransport class that uses urllib2 to
implement the HTTP transport.   It works around a bug in
urllib2 [handler ordering] and augments the request dispatch
found in the Transport class.

I'm using it in a production context and have tested it
fairly heavily.

I will be second to emphasize the importance of using XML-RPC through a
proxy. bzr behind a proxy can't be used with launchpad because of this bug.

Somebody else here in desperate need of this bug being fixed, both to
talk to bazaar and bugzilla...

It's a missing feature, not a bug in the existing code.  But if you're
desperate, why not just use the transport implementation that's attached
to this issue?

Well, strictly speaking, yes. It just feels like a rather major omission
(when Python can do xmlrpc and handle proxies you hope it will handle
the combination).

"Desperate" doesn't really have a timeline, strangely enough :) I know I
will be talking to bazaar and bugzilla behind a proxy in the mid-term
future and it would be very useful to use an officially sanctioned
solution (though of course I will try the attached file if there isn't
one at the time).

I see Python 2.6 is nearing release candidates : is this likely to be
included or will we have to wait for 2.7 now?

Would this be solved by issue1424152?

Could someone take a look at this while investigating other xmlrpc issues e.g. #7727.