Updating ultrajson#1
Open
WilliamBinquet wants to merge 789 commits into
Open
Conversation
updates: - [github.com/asottile/pyupgrade: v2.34.0 → v2.38.2](asottile/pyupgrade@v2.34.0...v2.38.2) - [github.com/psf/black: 22.6.0 → 22.8.0](psf/black@22.6.0...22.8.0) - [github.com/PyCQA/flake8: 4.0.1 → 5.0.4](PyCQA/flake8@4.0.1...5.0.4)
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
Doing so allows for building on webassembly. Officially declareing support for WASM however will have to wait until pyodide/pytest-pyodide#59 is merged to facilitate testing WASM compatibility.
Committed via https://github.com/asottile/all-repos
Due to a bug in PyPy [1], PyObject_GetBuffer() fails to detect non C contiguous inputs. Allowing ujson.loads() to run on non-contiguous buffers such as a strided NumPy array would lead to mayhem. Approximate the intention of PyObject_GetBuffer() by explicitly checking that the input is within the set of common bytes-like objects known to be unconditionally C contiguous. - [1]: https://foss.heptapod.net/pypy/pypy/-/issues/3872
updates: - [github.com/asottile/pyupgrade: v2.38.2 → v3.3.1](asottile/pyupgrade@v2.38.2...v3.3.1) - [github.com/psf/black: 22.8.0 → 22.12.0](psf/black@22.8.0...22.12.0) - [github.com/PyCQA/isort: 5.10.1 → 5.11.4](PyCQA/isort@5.10.1...5.11.4) - [github.com/PyCQA/flake8: 5.0.4 → 6.0.0](PyCQA/flake8@5.0.4...6.0.0) - [github.com/pre-commit/pre-commit-hooks: v4.3.0 → v4.4.0](pre-commit/pre-commit-hooks@v4.3.0...v4.4.0)
[pre-commit.ci] pre-commit autoupdate
There's some graalpy + virtalenv issue inside cibuildwheel and it doesn't look like we can do anything about it.
Given that it's impossible to even describe what serialising a concurrently mutating object is supposed to do, this is as far as I think is useful or feasible to go towards supporting it (#684/#689). Increasing the bug/CVE surface to include allowing any object to metamorph in any way at any time is really not what this code base needs.
* Fix off by one errors in detecting end of string mid sequence * Add missing check for codepoints > max unicode * Add missing check for bad continuation bytes
GraalPy's str.decode() error spells utf-8 as utf_8. Also add testing on ubuntu+graalpy to CI
Similar to 169eaf3 but for `ujson.loads(b'"garbled utf-8 stuff"')`. Fixes: * Continuation bytes without preceding start byte being silently coerced into other characters. * SystemError when decoding a 4-byte character > MAX_UNICODE (caused by us not checking then PyUnicode_New() complaining about what we gave it). (#716) * Allowing continuation bytes with an invalid second bit (0b11xx_xxxx as opposed to 0b10xx_xxxx).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
17 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.