Hi Joe, On Thursday, April 11, 2019 at 4:56:05 PM UTC+2, Johannes Hoppe wrote: > > @Florian, since I had so many PRs pending review, I had to find other ways > to cause chaos ;) >
Hehe probably, the autocomplete stuff is on my todo for the sprints (and selenium is mainly waiting for a merge). I would suggest as a first step to separate the field names from the object > methods. Thanks to multi inheritance in Python this should be an easy > enough task. > Personally I do not think this should be the first thing to do. At least for me the most common way to login is still an identifier + a password in combination with a second factor. And since u2f/totp/webauth do not really need anything from the usermodel aside from a PK for a foreignkey or so, this would be a good starting point. I think that, if needed, cleaning up the user model would be technically easy but hard from a backwards compatibility perspective. Introducing a new authentication flow/pipeline while technically hard would probably be relatively easy to add (new feature and settings while still supporting the old ones for a while). I will look into it a bit and propose something as a base for discussion. > Yes please, the more written things we have the more we can discuss it and have something concrete getting out of it. Cheers, Florian -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ed051fa5-e65d-45dc-863e-7f81885b5be8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
