Georg Brandl ge...@python.org added the comment:
Thanks, applied in r85543 and r85544.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4785
___
Tal Einat talei...@users.sourceforge.net added the comment:
Documentation patch attached against py3k branch.
Changes are:
* Added to documentation of JSONDecoder:
If *strict* is ``False`` (``True`` is the default), then control characters
will be allowed inside strings. Control characters
Tal Einat talei...@users.sourceforge.net added the comment:
Similar patch against trunk; same changes as for the py3k branch.
--
Added file: http://bugs.python.org/file17561/json_docs_trunk.diff
___
Python tracker rep...@bugs.python.org
Changes by Tal Einat talei...@users.sourceforge.net:
--
versions: +Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4785
___
___
Tal Einat talei...@users.sourceforge.net added the comment:
This goes down into _json.scanstring. Looking at the C code for
scanstring_unicode, the strict parameter allow control characters inside
strings: if strict is zero then literal control characters are allowed. From
the code itself
Tal Einat talei...@users.sourceforge.net added the comment:
This goes down into _json.scanstring. Looking at the C code for
scanstring_unicode, strict=False allows control characters inside strings: if
strict is zero then literal control characters are allowed. From the code
itself (current
New submission from David M. Beazley beaz...@users.sourceforge.net:
The strict parameter to JSONDecoder() is undocumented and is confusing
because someone might assume it has something to do with the encoding
parameter or the general handling of parsing errors (which it doesn't).
As far as I
