[issue12001] Extend json.dumps to handle N-triples strings

2011-05-06 Thread Terry J. Reedy
Terry J. Reedy added the comment: I agree that the json module should stick with the json definition. Adding other stuff would take it even further from simplejson. A conversion function, if short enough, could be posted on the cookbook. -- nosy: +terry.reedy resolution: -> rejected s

[issue12001] Extend json.dumps to handle N-triples strings

2011-05-06 Thread Éric Araujo
Éric Araujo added the comment: Agreed. The purpose of the json module is clearly defined, and there is room for other modules to address other problems (like yaml). It should be easy to write a Python function to convert a string to its N-triples serialization. -- nosy: +eric.araujo

[issue12001] Extend json.dumps to handle N-triples strings

2011-05-06 Thread Raymond Hettinger
Raymond Hettinger added the comment: Feature creep would not be good for the json module. -- ___ Python tracker ___ ___ Python-bugs-l

[issue12001] Extend json.dumps to handle N-triples strings

2011-05-06 Thread Antoine Pitrou
Antoine Pitrou added the comment: I'm not sure there's any sense in trying to bend the json module into producing other formats. -- nosy: +pitrou, rhettinger ___ Python tracker ___

[issue12001] Extend json.dumps to handle N-triples strings

2011-05-04 Thread Ezio Melotti
Changes by Ezio Melotti : -- components: +Library (Lib) nosy: +ezio.melotti versions: +Python 3.3 -Python 2.7, Python 3.4 ___ Python tracker ___ _

[issue12001] Extend json.dumps to handle N-triples strings

2011-05-04 Thread Glenn Ammons
New submission from Glenn Ammons : The string format used in N-triples is very similar to that used in JSON (see http://www.w3.org/TR/rdf-testcases/#ntrip_strings). It would be handy if json.dumps could (optionally) follow the N-triples format. The differences are 1) In \u escapes, the hexad