Re: [Django] #34002: PasswordResetView should work with AbstractBaseUser subclasses without is_active field. (was: PasswordResetView cannot find is_active property of User model extending AbstractBaseUser)
Django
is_active field.
-------------------------------------+-------------------------------------
Reporter: Brylie Christopher | Owner: nobody
Oxley |
Type: New feature | Status: closed
Component: contrib.auth | Version: 4.1
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* type: Uncategorized => New feature
* resolution: invalid => wontfix
Comment:
> I still believe this is a bug for a couple of reasons.
Documented behavior cannot be called a bug (it's documented since
f0425c72601f466c6a71518749c6d15b94945514). Password reset views/forms make
various assumptions about the user model and all of them are documented.
As far as I'm aware you're proposing a new feature. You can always define
your own subclass of `PasswordResetForm` and override the `get_users()`
method.
As it's a long standing behavior in a security-related area, I'm closing
this as "wontfix" with a request for a discussion on the mailing list, so
please first start a discussion on the DevelopersMailingList, where you'll
reach a wider audience and see what other think. Also,
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features follow the guidelines with regards to
requesting features]. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/34002#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.