Simplejson

Latest version: v3.19.2

Safety actively analyzes 629306 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 17 of 18

1.8.1

Not secure
* Optional C extension for accelerating the decoding of JSON strings
* Command line interface for pretty-printing JSON (via python -msimplejson)
* Decoding of integers and floats is now extensible (e.g. to use Decimal) via
parse_int, parse_float options.
* Subversion and issue tracker moved to google code:
http://code.google.com/p/simplejson/
* "/" is no longer escaped, so if you're embedding JSON directly in HTML
you'll want to use .replace("/", "\\/") to prevent a close-tag attack.

1.7

Not secure
* Improves encoding performance with an optional C extension to speed up
str/unicode encoding (by 10-150x or so), which yields an overall speed
boost of 2x+ (JSON is string-heavy).
* Support for encoding unicode code points outside the BMP to UTF-16
surrogate code pairs (specified by the Strings section of RFC 4627).

1.6

Not secure
* Improved str support for encoding. Previous versions of simplejson
integrated strings directly into the output stream, this version ensures
they're of a particular encoding (default is UTF-8) so that the output
stream is valid.

1.5

Not secure
* Better Python 2.5 compatibility
* Better Windows compatibility
* indent encoding parameter for pretty printing
* separators encoding parameter for generating optimally compact JSON

1.3

Not secure
* The optional object_hook function is called upon decoding of any JSON
object literal, and its return value is used instead of the dict that
would normally be used. This can be used to efficiently implement
features such as JSON-RPC class hinting, or other custom decodings of
JSON. See the documentation for more information.

1.1

Not secure
* Renamed from simple_json to simplejson to comply with PEP 8 module naming
guidelines
* Full set of documentation
* More tests
* The encoder and decoder have been extended to understand NaN, Infinity, and
-Infinity (but this can be turned off via allow_nan=False for strict JSON
compliance)
* The decoder's scanner has been fixed so that it no longer accepts invalid
JSON documents
* The decoder now reports line and column information as well as character
numbers for easier debugging
* The encoder now has a circular reference checker, which can be optionally
disabled with check_circular=False
* dump, dumps, load, loads now accept an optional cls kwarg to use an
alternate JSONEncoder or JSONDecoder class for convenience.
* The read/write compatibility shim for json-py now have deprecation warnings

Page 17 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.