Author bhargav
Recipients bhargav, bquinlan, bra, loewis
Date 2010-07-24.15:49:05
SpamBayes Score 0.00805605
Marked as misclassified No
Message-id <1279986547.47.0.0470121231578.issue8792@psf.upfronthosting.co.za>
In-reply-to
Content
What I do is not a possible solution, because some other machine might add e:nil, what we need is XML namespace parsing.

Also I can't really use my solution, as it makes my client non-portable, I cant move it from my dev machine to production at all.

This is just a workaround so that I am not stuck at ex:nil for my development.

I am not an expert in xmlrpc nor in python to really contribute a patch, but if I could really do think of something, I will contribute it.

Having said that, I know for sure the server works for Java clients and I have heard it works for .Net.

I know this is not a standard, but a widely used and published extension, and hence I think we should atleast port it back to the 2.7 branch as not everyone has moved to python 3 yet.
History
Date User Action Args
2010-07-24 15:49:07bhargavsetrecipients: + bhargav, loewis, bquinlan, bra
2010-07-24 15:49:07bhargavsetmessageid: <1279986547.47.0.0470121231578.issue8792@psf.upfronthosting.co.za>
2010-07-24 15:49:05bhargavlinkissue8792 messages
2010-07-24 15:49:05bhargavcreate