py38(django 2.2): upgrade django-picklefield to 2.1.0 #28317
Merged
+5
−20
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.
django-picklefield 2.1.0 adds support for Django 2.2 and drops all older Djangoes. However, it's still gonna work fine for Django 2.1, they just removed testing for it: gintas/django-picklefield@v2.0.0...gintas:v2.1.0
1.0.0 to 1.1.0 is also just some testing changes. The changes from 1.1.0 to 2.0.0 are minimal and are limited to:
PickledObjectField.We don't have any defaults set for our EncryptedPickledObjectFields; doesn't apply.
PickledObjectField. That makes.save(),.create(), etc. raiseIntegrityErrorif null is notTrueand no default value was specified like built-in fields do.We don't specify null=True on our EncryptedPickledObjectFields, and there are some in production with empty string values, so I've set empty_strings_allowed = True.
Since the fix introduced in #18934 is also now redundant, I've removed it as well.