#23406: Migrations not found when only .pyc files are available (e.g. in a
frozen
environment)
-------------------------------------+-------------------------------------
Reporter: Daniel Menzel | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: migrations, .pyc, | Triage Stage: Accepted
frozen, cx_Freeze |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dylan Young):
While I don't agree with the conclusion here (migration files *are*
explicitly imported when you run migrate; leftover .pyc files are a
tooling problem... think post checkout hooks), if this is the route to go
(and it's probably wise to do this anyways for other use-cases), I would
suggest that the setting to control this behaviour simply be
MIGRATION_LOADERS (as opposed to a tuple of extensions to support, for
example) and supply default loaders (.py, .pyc, archive) with hooks for
subclassing/creating new migration loaders. The setting would be a
tuple/list and the loaders would be consulted in list order (avoids the
need to mixin for every extension you want to support). This would also
allow things like a network loader for example.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:19>
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.15ab5ba7931f7e8aa89da58a6ca78d64%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
