This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Add a JSON-RPC module
Type: enhancement Stage:
Components: Versions: Python 3.1, Python 2.7
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: rhettinger Nosy List: loewis, rhettinger
Priority: normal Keywords:

Created on 2009-02-04 20:11 by rhettinger, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg81153 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2009-02-04 20:11
Add a JSON analogue to xmlrpclib.  See: 
 http://en.wikipedia.org/wiki/JSON-RPC

In some ways, it is much nicer than its XML cousin with bi-directional
communication, faster/simpler parsing, and ability to use TCP/IP
directly (not requiring HTTP transport).
msg81157 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2009-02-04 20:21
I think this feature request is out of scope for this bug tracker. To
fulfill the request, one not only has to *add* the module, but to
*implement* it first.

Since there is no inherent need for such a module to be provided with
the standard library, somebody implementing it should well first publish
it on PyPI, build a community, have it used for some time, and then
propose it for inclusion (e.g. through this bug tracker). That's the
same route that the XML-RPC implementation took.

If nobody volunteers to implement such a module, chances are high that
it is because nobody actually needs a Python implementation of a
JSON-RPC client module.
msg81216 - (view) Author: Raymond Hettinger (rhettinger) * (Python committer) Date: 2009-02-05 15:09
This is a reminder to me to submit a patch.
msg81226 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2009-02-05 20:26
> This is a reminder to me to submit a patch.

Is it really necessary to use the public bug tracker for that? All other
committers, as well as users, will see your reminder, and get bothered
by this (non-)issue.
History
Date User Action Args
2022-04-11 14:56:45adminsetgithub: 49402
2009-02-05 21:12:54rhettingersetstatus: open -> closed
2009-02-05 20:26:47loewissetmessages: + msg81226
2009-02-05 15:09:16rhettingersetmessages: + msg81216
2009-02-04 20:21:36loewissetnosy: + loewis
messages: + msg81157
2009-02-04 20:11:29rhettingercreate