#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 |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
I understand the use case. (I would guess that none of your other six
dependencies have a situation with similar constraints to Django migration
files). As I said before, I'm in favor of a patch that would change your
case from "Django needs patching" to "Django needs a non-default
flag/setting." That's why this ticket is in Accepted state. It's just
waiting for a patch that implements it as a non-default option.
I also agree with Shai that a setting is more appropriate than a flag,
because this is a property of a deployment, not a particular invocation.
(There remains an open question about zipfiles, I guess. I have no problem
with supporting zip-import by default, but I'm not sure if it's possible
to do that without also supporting `.pyc` by default, which is
problematic.)
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:18>
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.8cc98972f8452280e65a8847e3d054f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
