#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 jdetaeye):
For what it's worth, a patch is attached for this issue. It allows
migrations in any package format to be picked up, be it zip, egg, file,
...
> I think the practical hassles that causes to daily development with e.g.
git branches outweigh the purity of using the proper Python API for module
discovery."
I don't agree with this comment.
IMHO, a migration is a python package just like any other, and should be
treated as such.If some development practices have an issue with that it's
their problem - not django's.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:14>
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.9c21e680c9bc8a96d3da61186005a9c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
