#23406: Migrations not found when only .pyc files are available (e.g. in a
frozen
environment)
-------------------------------------+-------------------------------------
Reporter: Daniel Menzel | Owner: Dan
| Watson
Type: Bug | Status: assigned
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: migrations, .pyc, | Triage Stage: Accepted
frozen, cx_Freeze |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Dan Watson):
* owner: nobody => Dan Watson
* status: new => assigned
* has_patch: 0 => 1
Comment:
Reviving this ticket a little bit. I think something like this can be
useful in container environments, where you can guarantee pyc files are
generated with the same python binary being used to run them, mitigating
most of the drawbacks listed in
https://www.curiousefficiency.org/posts/2011/04/benefits-and-limitations-
of-pyc-only.html (an oldie but a goodie).
Created a pull request for a new `MIGRATIONS_INCLUDE_PYC` setting,
complete with docs and tests:
https://github.com/django/django/pull/9718
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:20>
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.5980ff32a718a91f024aae1fc4fc691f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
