#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: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Replying to [comment:28 Tim Graham]:
> Is there a disadvantage to waiting to revert
51673c146e48ff6230eace39bac18fd555607bee until after Python 2 is end-of-
life in 2020? I'm not really sure, but ignoring of pyc files may still
have some value as long as third-party apps support Python 2 and 3.
I can't quite see how an issue would come up (given that this would go
into Django 2.1, which is Python 3 only) but I can't rule it out either.
(There's nothing so weird and wonderful as programming. :)
There's no disadvantage really. Dan's PR is clean enough. If we're not
going to revert 51673c14 (and not go for wontfix) I think we should re-
open the PR and treat it as Ready for checkin, for a final review from
you. (I was at the point of marking it so, bar the revert option coming
up.)
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:29>
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.61e221f1cb1a340df970cd52ea26348a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
