#23406: Migrations not found when only .pyc files are available (e.g. in a
frozen
environment)
-------------------------------------+-------------------------------------
Reporter: danielmenzel | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: migrations, .pyc, | Triage Stage: Accepted
frozen, cx_Freeze | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by andrewgodwin):
If it was to work correctly, it would need to be passed to
`makemigrations`, `migrate`, `sqlmigrate` and `squashmigrations`, but I
suspect we could get away with just adding it to `migrate` and
`sqlmigrate`? I'm still not sure about that, but seems better than a
setting.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#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/070.790e31acae7551f85ab8224f57304d16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
