On Sat, Jun 20, 2009 at 6:57 PM, Martin v. Löwismar...@v.loewis.de wrote:
Fredrik Lundh wrote:
I think you really need to get Fredrik Lundh to comment on it. If he
can't predict when he'll be able to review the changes, maybe he can
accept releasing control of xmlrpclib.
Pointer to the
On Sat, Jun 20, 2009 at 6:57 PM, Martin v. Löwismar...@v.loewis.de wrote:
While I have your attention, please also review
http://bugs.python.org/issue6233
I'm pretty sure that fix is the wrong fix - afaik, _encode is used to
encode tag/attribute names, and charrefs don't work in that context.
Fredrik Lundh wrote:
On Sat, Jun 20, 2009 at 6:57 PM, Martin v. Löwismar...@v.loewis.de wrote:
Fredrik Lundh wrote:
I think you really need to get Fredrik Lundh to comment on it. If he
can't predict when he'll be able to review the changes, maybe he can
accept releasing control of xmlrpclib.
I‘d really like to get this stuff in. The performance gains allowing
http1.1 and gzip for xmlrpc are quite significant.
I think you really need to get Fredrik Lundh to comment on it. If he
can't predict when he'll be able to review the changes, maybe he can
accept releasing control of
2009/6/20 Martin v. Löwis mar...@v.loewis.de:
I‘d really like to get this stuff in. The performance gains allowing
http1.1 and gzip for xmlrpc are quite significant.
I think you really need to get Fredrik Lundh to comment on it. If he
can't predict when he'll be able to review the changes,
Fredrik Lundh wrote:
I think you really need to get Fredrik Lundh to comment on it. If he
can't predict when he'll be able to review the changes, maybe he can
accept releasing control of xmlrpclib.
Pointer to the patch?
http://bugs.python.org/issue6267
While I have your attention, please
Hello there.
I've been trying to, in the last weeks, to pass on to the trunk the
improvements I've made to XMLRPC.
I've created several issues in order to do these changes incrementally but have
got no comments.
Perhaps it is best to show the whole thing in context, then.
I´ve gathered all the
