#31592: Reverting Django 3.1. to Django 3.0.6 raises "binascii.Error: Incorrect
padding".
------------------------------+--------------------------------------
     Reporter:  אורי          |                    Owner:  nobody
         Type:  Bug           |                   Status:  closed
    Component:  Core (Other)  |                  Version:  3.1
     Severity:  Normal        |               Resolution:  invalid
     Keywords:                |             Triage Stage:  Unreviewed
    Has patch:  0             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  0             |                    UI/UX:  0
------------------------------+--------------------------------------

Comment (by felixxm):

 Replying to [comment:3 אורי]:
 > Does this error also occur if I migrate forward (from 3.0 to 3.1) ...?
 >

 No, support for user sessions that use the old hashing algorithm remains
 until Django 4.0, see [https://docs.djangoproject.com/en/3.1/releases/3.1
 /#django-contrib-auth release notes].

-- 
Ticket URL: <https://code.djangoproject.com/ticket/31592#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.bac6728d192fc5d08e8e8c03d3223962%40djangoproject.com.

Reply via email to