[PATCH v2 0/3] pwclient: python 3 and proxy support

These patches should close the issues #47 and #59 by adding proxy support and fixing authentication (for write operations) with Python 3. Note: I have not tested with https. The last patch tries to fix the strings and patch files with Python 3. I am not sure to understand all these encoding stuff

[PATCH v2 3/3] pwclient: Fix Python 3 encoding of received strings

The conversion encode("utf-8") makes a byte stream which is poorly printed with Python 3. However this encoding is required for Popen.communicate() but must be done after str.join() which applies to a real string. Signed-off-by: Thomas Monjalon Reviewed-by: Stephen

[PATCH v2 2/3] pwclient: Support proxy configuration

The environment variables http_proxy and https_proxy can be used to configure the HTTP transport. The TCP connection is made with the proxy host, whereas the original host is maintained in the HTTP POST URI via "handler" in "send_request". The send_request() method of xmlrpclib has a different

[PATCH 0/1] xmlrpc: Expose patch hash to patch_get

Hi all, This simple patch exposes the "hash" value of a patch object. With the patchwork instance that we run, our software development model makes us do a round of internal submissions first, and then a final upstream submission. This can cause the same patch hash to appear several time for

[PATCH 1/1] xmlrpc: Expose patch hash to patch_get

Expose the patch object hash value to xmlrpc::patch_get. This is particuarly helpful if some patche(s) have been submitted several times but changed from e.g: RFC to a proper official patch submission. The hash would typically be identical, but numbers would not. Signed-off-by: Florian Fainelli