#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
-------------------------------------+-------------------------------------
Comment (by Dan Watson):
I'm actually in favor of reverting. Hadn't considered that now that Django
is Python 3 only. If you have legacy stale pyc files, it's because you
compiled them yourself now, which means you'd probably be using this
setting. So why have the setting at all :)
I wonder what Python 3 does when it sees a pyc file compiled with Python
2. That would be the only place I could see breakage for existing projects
with old Python 2 pyc files hanging around, but my guess is that they'd be
ignored (or fail loudly and hopefully obviously).
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:25>
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.839e0100e8bc2979cffc05333dff8dd8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
