#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 shaib):
Yeah, the idea to add an app was mostly a way to do this in settings.py
without introducing a new setting.
So I take that back. But the main point remains: The determination of how
migrations are found is a property of the deployment, not a property of a
single invocation of migration commands. A setting is much better than a
flag.
On a related note, the setting should probably be more general than just
"use .pyc's". What about finding migrations in zip files? I can come up
with a couple of less likely candidates as well.
So yes, scratch the app overriding the commands. We need a setting to
specify the path to a migration loader, and we probably need to ship,
along with the standard loader, one which picks up .pyc files (and maybe
one which peeks in archives).
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:10>
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.9e705daae23eed1a142e3d6fb3c34690%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
