json262
JSON encoder fully compliant with ECMA-262 specification.
Free software: BSD license
Documentation: http://json262.readthedocs.org.
Features
Support for all objects that the Python stdlib’s json.JSONEncoder can encode, plus:
datetime.datetime
datetime.date
datetime.time
decimal.Decimal
Works on Python 2.6, 2.7, 3.3. Probably works on 3.4 and 3.5 but I haven’t set up tests for those with Tox yet.
Quickstart
Use JSON262Encoder as you would use json.JSONEncoder from the Python standard library:
>>> import datetime
>>> import json
>>> from json262 import JSON262Encoder
>>> json.dumps({'day': datetime.date(2010, 2, 17)}, cls=JSON262Encoder)
'{"day": "2010-02-17"}'
History
0.2.0 (2014-05-20)
Full implementation with tests.
Separate encoders module for encoder functions.
Bump to Alpha.
0.1.0 (2014-05-18)
First release on PyPI.
1 maintainer
Metadata
1 maintainer
Release files for json262 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| json262-0.2.0.tar.gz | 12.3 kB | Without provenance | Details for json262-0.2.0.tar.gz |
Release files / json262-0.2.0.tar.gz
| Download URL | json262-0.2.0.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba3453bebd413914d10864da2e752d8293c42a4ef52058a13f80afa195716b43
|
|
BLAKE2b-256 checksum How to use checksums |
c2806e5ff3489a393fde849dffbdebbc942bda87139d051588e20eb8dcaeea8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for json262 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
