#31842: django.core.signing.dumps() and loads() not backwards compatible
-----------------------------------+------------------------------------
Reporter: Markus Holtermann | Owner: felixxm
Type: Bug | Status: closed
Component: Core (Other) | Version: 3.1
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"d907371ef99a1e4ca6bc1660f57d81f265750984" d907371e]:
{{{
#!CommitTicketReference repository=""
revision="d907371ef99a1e4ca6bc1660f57d81f265750984"
Fixed #31842 -- Added DEFAULT_HASHING_ALGORITHM transitional setting.
It's a transitional setting helpful in migrating multiple instance of
the same project to Django 3.1+.
Thanks Markus Holtermann for the report and review, Florian
Apolloner for the implementation idea and review, and Carlton Gibson
for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31842#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.df1d14c819f8c494e212d946f6e32e64%40djangoproject.com.
