#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):
I think migrate and sqlmigrate are the only required ones for the use-case
(you don't generate or manipulate migrations in a frozen environment).
But I don't like the flag approach -- it essentially passes the problem
from the developer to their user.
I think the correct approach is an app that overrides ("enhances", if you
like) the built-in migration commands, in much the same way that South
enhanced `syncdb`. If it is hard to write as a 3rd-party app, we should
make the changes required to make it easy.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:7>
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/070.7dbf4d7c29473ac2205d68d3602ed349%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
