#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: Ready for
frozen, cx_Freeze | checkin
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
The "some advantage" is in being able to ship a `.pyc` only version of you
code. This isn't something I've done but, reviewing the issue it seemed a
reasonable use-case. (The discussion ≈3 years ago didn't close...)
As far as I can see, in this Python 3 world you're only going to run into
this if you're deliberately creating the legacy `.pyc` files. In that case
you should already know what you're doing.
You're not going to hit anything that a `find . -name '*.pyc' -delete`
won't fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:33>
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.081307317ca76eb1e41b9c156c8daa74%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
