django__django-13279

Session data cannot be decoded during the transition to Django 3.1.

Verdict: the fix is stated in the issue (Tier A).

We could use the legacy encode() when DEFAULT_HASHING_ALGORITHM == 'sha1' (it's a bit hacky).

The text states the fix: “We could use the legacy encode() when DEFAULT_HASHING_ALGORITHM == 'sha1' (it's a bit hacky).”

All SWE-bench Verified tasks · more django/django tasks · How the check works