#22459: Creating model classes for test purposes breaks migrations
--------------------------------------+------------------------------------
Reporter: pgcd | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
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 claudep):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Note that I was also confronted to this while trying to provide initial
migrations for contrib.auth app (#22170). I workarounded it by also adding
a migrations folder in the tests, and specifying `MIGRATION_MODULES` (see
https://github.com/claudep/django/commit/05af8e787e22e5fd5894fd1f3069df7a9fd40fc3).
But It's definitely a realm where a better solution should be provided.
--
Ticket URL: <https://code.djangoproject.com/ticket/22459#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.b424cdb0b36ea91f52897735c57da9a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
