Bruno Gomes wrote:
> Oh, and one more thing: if I just say "bzr branch lp:project" instead of
> giving the full URL, it doesn't use the proxy settings. I remember
> reading something about it being a limitation when I first opened this
> bug, but it's been such a long time that I don't remember what it was
> anymore. Could anybody clear that up for me?
>
However, it seems that python's xmlrpc library doesn't have native
support for proxies. So it will require a bunch of development on our
part to sneak in proxy support.
It is an open bug, though I don't have the number offhand.
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bruno Gomes wrote:
> Oh, and one more thing: if I just say "bzr branch lp:project" instead of
> giving the full URL, it doesn't use the proxy settings. I remember
> reading something about it being a limitation when I first opened this
> bug, but it's been such a long time that I don't remember what it was
> anymore. Could anybody clear that up for me?
>
lp:project uses XMLRPC to resolve lp:project => http://....
However, it seems that python's xmlrpc library doesn't have native
support for proxies. So it will require a bunch of development on our
part to sneak in proxy support.
It is an open bug, though I don't have the number offhand.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
Br9kACgkQJdeBCY SNAAO5ogCgp1ngp bDAq1iGL8sEwlGl Omvb nwu4xOBfXp0fHDq E0CE
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq
GUYAoLXaZQ7Q+
=xttH
-----END PGP SIGNATURE-----