#23473: Django prompts to create new migrations when none are needed when a
class
is used in a field declaration
----------------------------+------------------------------------
Reporter: dlo | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Changes (by Markush2010):
* stage: Unreviewed => Accepted
Comment:
I can confirm this behavior. I suggest to document the requirement for a
`__eq__` method.
--
Ticket URL: <https://code.djangoproject.com/ticket/23473#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.24bf0b569c222b7cb657de347cda25ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
