#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 carljm):
Replying to [comment:14 jdetaeye]:
> IMHO, a migration is a python package just like any other, and should be
treated as such.
It's not a package like any other, because normal Python packages don't
have an effect on the system unless explicitly imported.
> If some development practices have an issue with that it's their problem
- not django's.
Your patch will cause serious, difficult to debug problems for any
development practice which involves adding and removing Python modules
(including migrations) from source code under local development, while
ignoring `pyc` files. (I know this is the case, because for a period of
time in the 1.7 development process, orphan `pyc` files were loaded as
migrations, and it did cause these problems.) I think you would be hard
pressed to find any current common Django development process that doesn't
fit that description.
If you have a practical proposal for how to address that problem (whether
with documentation changes or otherwise) in your patch, I'm interested in
discussing it. If you think it's "not Django's problem" and can be
ignored, I'm afraid we just disagree, and I have to remain -1 on merging
your patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:15>
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.7ba16928d444c19093537166d1b0139f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
