[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Martin v. Löwis added the comment: In case it isn't clear from the discussion in issue8792: I'd be in favor of supporting extensions as long as their usage is an opt-in feature. The current nil support is already an opt-in feature. If alternative spellings of nil need to be supported, or othe

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Éric Araujo added the comment: There's no need to apologize, we welcome contributions like your report and are open to discuss patches :) -- ___ Python tracker ___

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Changes by Éric Araujo : -- superseder: -> Support Apache extensions to XML-RPC in xmlrpclib ___ Python tracker ___ ___ Python-bugs-l

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Changes by Senthil Kumaran : -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Adam Bielański added the comment: It is. It might go. Didn't notice issue8792 before, thanks for pointing it out. Whole ex:nil issue is discussed there, so this issue might be closed. -- ___ Python tracker __

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Senthil Kumaran added the comment: On Tue, Nov 16, 2010 at 11:32:03AM +, Adam Bielański wrote: > just accept ex:nil as well as nil and not try to analyze namespaces at all. But even that seems specific to Java/ Apache Extension. If it is, then it might go in as part of issue8792.

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Adam Bielański added the comment: Ok, I apologize for being to hasty. Below you can find my answers: 1. SlowParser used in xmlrpclib doesn't deal with namespaces in any reasonable way. If there's a namespace prefix for tag, it's not separated from tag name, but passed as part of tag name. But

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Éric Araujo added the comment: Thanks for the report and patch. You may find the following guidelines useful for your future contributions: http://www.python.org/dev/patches/ I have two questions about the proposed fix. First, this line caught my eye: if tag.split(':')[1] == 'nil': It se

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

Changes by Senthil Kumaran : -- assignee: -> orsenthil nosy: +orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue10425] xmlrpclib support for None isn't compliant with XMLRPC

New submission from Adam Bielański : XMLRPC standard doesn't support None/nil/null values. Element `` was added as an extension to original protocol. Currently sending None object through xmlrpclib produces `` string. This causes parsing errors in more sophisticated XMLRPC parsers (like org.a