#32868: Add system check or warning for model fields shadowing methods / other
attributes
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: nobody
Type: New feature | Status: closed
Component: Core (System | Version: dev
checks) |
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):
* cc: Carlton Gibson (added)
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this proposition, however I'm skeptical. I don't think it's
worth additional complexity and potential backward incompatibility. In
most of cases Django will already crash, e.g.
{{{
>>> obj.save()
TypeError: 'bool' object is not callable
>>> obj.delete()
TypeError: 'bool' object is not callable
}}}
The extra check added in #23615 was already a bit controversial (see
[https://github.com/django/django/pull/3362#discussion_r18836742
discussion]). You can raise the idea on the DevelopersMailingList to reach
a wider audience and see what other think.
--
Ticket URL: <https://code.djangoproject.com/ticket/32868#comment:1>
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/068.e8cb8b2f6ce14248111e9cc40c1e6bce%40djangoproject.com.
