#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 Carlton Gibson):
* cc: Carlton Gibson (added)
Comment:
The patch as presented, and given the history of the ticket, looks great.
Ref [comment:22 comment from Andrew Godwin]:
> ... there are no longer any .pyc files in the migrations directory (they
go into __pycache__) in Python 3 ...
So, maybe the original problem (of stale .pyc files when switching
branches) has gone away? They'll only be there if you've taken deliberate
steps to make sure they are.
So can we just load them? Do we still need the setting? Do we need the
warning around the setting? Could we not now revert
[https://github.com/django/django/commit/51673c146e48ff6230eace39bac18fd555607bee
51673c14], which was Andrew's commit restricting the search to just `.py`
files?
Assuming we don't want to revert, I'm inclined to call this Ready for
checkin.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:24>
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.7c39500bfe31bbaf67688edc2157324e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
