On Saturday, August 1, 2020 at 7:16:57 AM UTC+2 Uri wrote:
> How do you propose running several versions of Django 3.0 and 3.1 with > this PR and setting? Does it have to be defined, or is it enough using the > default setting? > You have to set it to `sha1` and then when all your instances upgraded to 3.1 you will can remove it at which point all new signatures will use the new algorithm. And when upgrading Django to 3.1, what is the default setting if this > setting is not explicitly defined? And how will it affect sessions in case > of downgrading back to 3.0? Will it be possible to downgrade also with the > default setting? > Downgrading will __never__ be supported. This is only for the transitional period where you run 3.0 and 3.1 in tandem. Once you switched to 3.1 and changed fully to `sha256` there will be no way (never ever!) to downgrade that. And also, how to define this setting to its default value in Django > versions <= 3.0. > You don't, this is not supported. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7f76827b-a259-437c-8c22-2c4b18e5753cn%40googlegroups.com.
