[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Senthil Kumaran added the comment: Addressed this in all active branches (2.7, 3.3 and 3.4). Thanks! -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Roundup Robot added the comment: New changeset 1730f4a97cbb by Senthil Kumaran in branch '2.7': Issue #19082: Working SimpleXMLRPCServer and xmlrpclib examples, both in modules and documentation. http://hg.python.org/cpython/rev/1730f4a97cbb New changeset 72560f9bb2a2 by Senthil Kumaran in bran

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Senthil Kumaran added the comment: Sounds good.I shall update patch (.rstify the security warning). Thank you! -- ___ Python tracker ___

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Vajrasky Kok added the comment: Hi, Senthil Kumaran, thank you for your review. I have one small complain about your improved patch. Perhaps we need to give security warning when they want to use allow_dotted_names feature in the documentation. I omitted the warning in the demo because it is j

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Senthil Kumaran added the comment: The patch is good. I think, it is better to include this information in documentation too. Please let me know if this suitable, I shall go ahead committing this. (With credits to Vajrasky Kok) -- assignee: -> orsenthil nosy: +orsenthil versions: +Pyt

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Vajrasky Kok added the comment: Okay, I updated the patch. Now, it sends the datetime object instead of formatted datetime string. Also, I used static method inside instance to let the client uses dotted attribute feature instead of self attribute trick. -- Added file: http://bugs.pyth

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

R. David Murray added the comment: Yeah, a new issue is probably a good idea. If the dotted attribute feature is not tested by test_xmlrpc, then the test is probably worth migrating. I'm not sure what to do about the docs, and that should be a separate issue as well. --

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Vajrasky Kok added the comment: What test_xmlrpc_net tests (especially the one with time.xmlrpc.com) have been tested in test_xmlrpc except for connecting to server with dotted_attribute feature and receiving datetime instance over the network. That test is not that hard to be migrated to test

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

R. David Murray added the comment: Sure :) If you want some bonus points, can you figure out whether or not the test in test_xmlrpc_net is worth moving to test_xmlrpc using a similar local-server approach, or if it is redundant and should just be deleted? (time.xmlrcp.com has come and gone mu

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Changes by Vajrasky Kok : Removed file: http://bugs.python.org/file31856/xmlrpc_server_client_demo.patch ___ Python tracker ___ ___ Python-bug

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Changes by Vajrasky Kok : Added file: http://bugs.python.org/file31857/xmlrpc_server_client_demo.patch ___ Python tracker ___ ___ Python-bugs-

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

New submission from Vajrasky Kok: Lib/xmlrpc/client.py tries to connect to http://time.xmlrpc.com/RPC2 which has been dead for a "while". I see there is no light in the end of tunnel. Since this code is meant to be a demo not a general purpose tool, I say why don't we direct it to localhost (w