[issue14674] Add link to RFC 4627 from json documentation

Éric Araujo added the comment: A message should have been sent to pyb...@rebertia.com. -- ___ Python tracker ___ ___ Python-bugs-list

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: So, does the refactored patch need any further revising, or is it good to go? -- ___ Python tracker ___ _

[issue14674] Add link to RFC 4627 from json documentation

Changes by Chris Rebert : Removed file: http://bugs.python.org/file25591/json.rst.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue14674] Add link to RFC 4627 from json documentation

Changes by Chris Rebert : Added file: http://bugs.python.org/file25606/json.rst.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue14674] Add link to RFC 4627 from json documentation

Changes by Chris Rebert : Removed file: http://bugs.python.org/file25592/json.rst.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: Notification of any future Rietveld comments would be appreciated. -- Added file: http://bugs.python.org/file25603/json.rst.patch ___ Python tracker

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: >> for key, value in pairs: >> if key in pairs: > > "if key in obj:"? Yes, obviously. :-) It wrote those very late at night. @Ezio: These were per Éric's feedback but would be for a separate bug/patch. -- _

[issue14674] Add link to RFC 4627 from json documentation

Serhiy Storchaka added the comment: IMHO, it would be sufficient to have a simple bullet list of differences and notes or warnings in places where Python can generate non-standard JSON (top-level scalars, inf and nan, non-utf8 encoded strings). -- __

[issue14674] Add link to RFC 4627 from json documentation

Serhiy Storchaka added the comment: > for key, value in pairs: > if key in pairs: "if key in obj:"? -- title: Link to & explain deviations from RFC 4627 in json module docs -> Add link to RFC 4627 from json documentation ___ Python trac

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: Further copyediting. -- Added file: http://bugs.python.org/file25595/json.rst.patch ___ Python tracker ___ __

[issue14674] Add link to RFC 4627 from json documentation

Ezio Melotti added the comment: Thanks for the patch, I left more comments on the review page. IMHO it would be better to list the differences in a bullet list and expand later, rather than having a section for the parser and one for the generator. AFAIU the differences are: * top-level scala

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: The "import json"s were left for uniformity with the other code samples in the module's docs. Also, here's what the pedantically-strict recipes might look like: def _reject_inf_nan(string): if string in {'-Infinity', 'Infinity', 'NaN'}: raise Value

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: New revision per Éric's Rietveld feedback. Sidenote: Is there any way to get notified of these reviews? I only saw it because I happened to click the "review" link on a lark. -- Added file: http://bugs.python.org/file25594/json.rst.patch __

[issue14674] Add link to RFC 4627 from json documentation

Changes by Chris Rebert : Added file: http://bugs.python.org/file25592/json.rst.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue14674] Add link to RFC 4627 from json documentation

Chris Rebert added the comment: Draft docs patch. More cross-referencing. Analysis of deviations from RFC based on previous docs & the RFC. Don't know if there are relevant, more precise implementation limitations that need to be mentioned. If backported to 2.x, will need to cover encodings

[issue14674] Add link to RFC 4627 from json documentation

Changes by Ezio Melotti : -- nosy: -Nurhusien.Hasen ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue14674] Add link to RFC 4627 from json documentation

Changes by Ezio Melotti : -- Removed message: http://bugs.python.org/msg160098 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue14674] Add link to RFC 4627 from json documentation

Changes by Ezio Melotti : -- Removed message: http://bugs.python.org/msg160089 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue14674] Add link to RFC 4627 from json documentation

Nurhusien Hasen added the comment: find python .org public all serves On 5/6/12, Nurhusien Hasen wrote: > > Nurhusien Hasen added the comment: > > find python truste .net all serves > > -- > nosy: +Nurhusien.Hasen > > ___ > Python tracker >

[issue14674] Add link to RFC 4627 from json documentation

Nurhusien Hasen added the comment: find python truste .net all serves -- nosy: +Nurhusien.Hasen ___ Python tracker ___ ___ Python-bug

[issue14674] Add link to RFC 4627 from json documentation

Changes by Ezio Melotti : -- nosy: +ezio.melotti versions: +Python 2.7, Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue14674] Add link to RFC 4627 from json documentation

Changes by Éric Araujo : -- keywords: +easy nosy: +eric.araujo stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue14674] Add link to RFC 4627 from json documentation

New submission from Serhiy Storchaka : The json module documentation should give a link to RFC 4627 and explain the current implementation is different from it. For example, according to RFC 4627 only an object or an array can be top-level JSON element. -- assignee: docs@python compone