> I think this just move the migration problem from 3.2 to 4.0. My thought was the instant warning helped with that... BUT...
What about the other way: add a migration setting set to new algorithm, so > who really need sha1 can opt-in to old algorithm? > Yes, perhaps: default to the future sounds better. > -- 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/CAJwKpySb-cyEhQwJVETef_UJ2Kuagyty%2BYcLMAZrMK9xaOzHNg%40mail.gmail.com.
