Fredrik Lundh wrote:
On Sat, Jun 20, 2009 at 6:57 PM, "Martin v. Löwis" 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 pa
On Sat, Jun 20, 2009 at 6:57 PM, "Martin v. Löwis" 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.
___
On Sat, Jun 20, 2009 at 6:57 PM, "Martin v. Löwis" 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 patch?
>
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, p
2009/6/20 "Martin v. Löwis" :
>> 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 c
> 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 xmlrpc
