#33441: Model Field.__hash__() should be immutable.
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Adam
| Johnson
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Johnson):
> Could you go into more detail about this statement? Fields meant to be
assigned/bound to a model class should all be set after the app setup
phase and no fields should be bound to a model class after this point so
I'm struggling to come up with the plenty of uses in ORM expressions you
are referring to. Just saying that providing concrete examples might help
your case here.
> I'm also struggling with finding "plenty of uses", nevertheless it
should not block this change .
Sorry, I wasn't clear. I meant: There are plenty of uses for fields in ORM
expressions. These *might* lead a user to create references to a field
before/after they are assigned to a model class. I don't have a concrete
example, and clearly it must be rare, since no one has reported a bug
since Django 3.2. But, I don't think it's inconcievable that someone will
try this at some point.
--
Ticket URL: <https://code.djangoproject.com/ticket/33441#comment:7>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.2a464dd3211d7303e15015435d5bc2c5%40djangoproject.com.
