New submission from Sandro Tosi <sandro.t...@gmail.com>: following up http://mail.python.org/pipermail/docs/2011-March/003506.html , I verified that indeed
http://www.xmlrpc.com/discuss/msgReader$1208 is broken. I wrote to d...@scripting.com (the address you get when viewing http://www.xmlrpc.com/discuss/) on march and just now I re-wrote again, but I got no reply and the link is still broken. I tried finding another source for the same doc, but it seems it's only available on xmlrpc.com (or some other dead links). I found, tho, the relative article on the wayback machine: http://web.archive.org/web/20060624230303/http://www.xmlrpc.com/discuss/msgReader$1208?mode=topic Now, what should we do about this? remove the link completely? but then how can a user find information about multicalls? should we incorporate that article in our doc (do the licences allow us?)? Cheers, Sandro ---------- assignee: docs@python components: Documentation messages: 142504 nosy: docs@python, ezio.melotti, sandro.tosi priority: normal severity: normal stage: needs patch status: open title: xmlrpc.client documentation (MultiCall Objects) points to a broken link versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12787> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
