#32130: 3.0 -> 3.1 password token incompatibility.
--------------------------------+--------------------------------------
Reporter: Gordon Wrigley | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution:
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 Gordon Wrigley):
We've been discussing using patchy to do something to that effect.
With free code access you can easily tell because the prefix is 3
characters in the old scheme and 6 in the other so you could switch off
that.
If you were to switch off value anything in the 10k (~27*365) -
600m(~19*365*60*60) range should be a safe cutoff.
--
Ticket URL: <https://code.djangoproject.com/ticket/32130#comment:3>
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.bb3b6c820984bd5bf788f41a397d0ba2%40djangoproject.com.
