#32035: AbstractUser.clean assumes default manager is named objects
-------------------------------+--------------------------------------
Reporter: Ben Brooks | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi Ben,
I'm struggling to understand whether this is a valid report or not.
> Our third-party app implements a generic view (with objects = None) and
set the default manager to be something else.
So either...
1. You're implementing a view, in which case this doesn't make much sense,
or
2. You're creating a custom user model, in which case if you're **not
happy** with the default model implementation you should be extending
`AbstractBaseUser` here.
Can I ask you to clarify?
Either way, it doesn't look like a valid report `User` and (by extension)
`AbstractUser` don't really satisfy the "an unknown model" part of the
docs you link.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/32035#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.a922596803aa755ce19a815eddd4ef29%40djangoproject.com.
