There's a ticket about it: https://code.djangoproject.com/ticket/27468
Backwards compatibility is the main consideration.
On Tuesday, May 8, 2018 at 6:44:05 PM UTC-4, Cristiano Coelho wrote:
>
> Looks like the Signer class (and perhaps other parts of the code) still
> use SHA1 ([1] and [2]) for
Looks like the Signer class (and perhaps other parts of the code) still use
SHA1 ([1] and [2]) for the HMAC signing/hashing process.
I'm wondering if there's any specific reason to use SHA1 over newer
versions, or if it would be worth it to pass the hash algorithm as a
variable or even config o
For future ref: this mailing list is for the development of Django itself,
not for support. Use the django-users mailing list for that, or IRC #django
on freenode, or a site like Stack Overflow.
On 8 May 2018 at 05:57, Pradeep Sharma wrote:
> check your models.py
>
> --
> You received this messa
check your models.py
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To p
