-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
encoding of \u2028 and \u2029 is incorrect #2
Comments
richvdh
added a commit
that referenced
this issue
Mar 28, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Mar 28, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Mar 28, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Mar 28, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Mar 28, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Mar 29, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Mar 29, 2018
This turns out to be way quicker. It also allows us to fix #2.
richvdh
added a commit
that referenced
this issue
Jun 4, 2018
This turns out to be way quicker. It also allows us to fix #2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the spec says that
\u2028
(line separator) should be encoded as the UTF-8\xe2\x80\xa8
, however python-canonicaljson encodes it as the\u
-escaped version.This is largely thanks to simplejson/simplejson#206.
The text was updated successfully, but these errors were encountered: