If we go to the most common use case, email + password is the current
"default" of the web, rather than username + password. It would make sense
for Django to use email + password by default.
It also feels like first_name and last_name have no place in AbstractUser
and should me moved to NamedA
Just out of curiosity, I was wondering if we got any traction on this.
On Monday, March 18, 2019 at 5:27:47 AM UTC-5, Carlton Gibson wrote:
>
> Hi all,
>
> Parallel to GSoC, Google now have this "Season of Docs" programme:
>
> https://developers.google.com/season-of-docs/
>
> The idea is experie
Hi Joe,
uff you are bringing up a hard topic :) Yes I absolutely would like Django
to have better support for WebAuth (u2f-like tokens at least), and probably
another one or two (I'd keep the scope for support in Django small though
once we know that the API works).
Getting this actually imple
Email + password auth is definitely a wanted feature out-of the box, and
probably a good first step would be to create a separate AbstractEmailUser
or something like that. Seems to me AbstractUser shouldn't be changed for
backwards compatibility reasons, but maybe something like a
BaseAbstractUser
Hi William.
A few people have shown interest so I will apply as an org for us. Then
candidates can apply. (I’m hopeful we could get multiple slots but it’s a
new programme so I don’t really know.)
C.
On Wed, 10 Apr 2019 at 21:03, William Hakizimana
wrote:
> Just out of curiosity, I was wonderi
Was looking into the docs issues and suddenly this come!!
On Thursday, April 11, 2019 at 12:08:27 PM UTC+6, Carlton Gibson wrote:
>
> Hi William.
>
> A few people have shown interest so I will apply as an org for us. Then
> candidates can apply. (I’m hopeful we could get multiple slots but it’s
