Update dependency jsonpickle to v4 #1847
Merged
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.
This PR contains the following updates:
3.4.2
->4.0.1
Release Notes
jsonpickle/jsonpickle (jsonpickle)
v4.0.1
Compare Source
======
* The unpickler is now more resilient to malformed "py/reduce", "py/set",
"py/tuple", "py/b64", "py/b85", and "py/iterator" input data. (+544) (+545)
* The test suite was updated to leverage more pytest features.
* The
jsonpickle.compat
module is no longer used. It is still providedfor backwards compatibility but it may be removed in a future version.
v4.0.0
Compare Source
======
* Breaking Change: Python 3.7 is no longer supported.
* Breaking Change: Support for pre-0.7.0
repr
-serialized objects is nolonger enabled by default. The
safe
option todecode()
was changed fromFalse
toTrue
. Users can still passsafe=False
todecode()
in orderto enable this feature for the purposes of loading older files, but beware that
this feature relies on unsafe behavior through its use of
eval()
. Users areencouraged to re-pickle old data in order to migrate away from the the unsafe loading
feature. (+514)
* The pickler no longer produces
py/repr
tags when pickling modules.py/mod
is used instead, as it is clearer and uses one less byte. (+514)* The test suite no longer uses the deprecated
datetime.datetime.utcnow()
function. (+539)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.