#23473: Django prompts to create new migrations when none are needed when a
class
is used in a field declaration
----------------------------+---------------------------------------
Reporter: dlo | Owner: Markush2010
Type: Bug | Status: assigned
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
----------------------------+---------------------------------------
Comment (by dlo):
Is there any way we could also make the `./manage.py makemigrations`
command fail unless `__eq__` is implemented? Otherwise, users might not
know where to look to fix the problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/23473#comment:6>
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.f3528c85f099fc1549bbb99370937f92%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
