#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):

 I'm not sure the fix for #8280 is actually appropriate here - I don't
 believe that by default orphan `.pyc` files should be considered as
 present migrations. 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.

 The distinction here is that usually the presence or absence of a module
 that hasn't been explicitly requested doesn't fundamentally alter the
 behavior of the system. With management commands, it does a bit (they'll
 show up in help) but not in a way that's likely to break anything. Here,
 having extra migrations around that shouldn't be around in this branch
 seriously breaks things.

 If we made migrations discover `.pyc` by default, we would basically have
 to document that `PYTHONDONTWRITEBYTECODE=1` is required for effective
 local development in Django.

 I'm not opposed to an option to enable `.pyc` discovery, but I am opposed
 to making it the default.

--
Ticket URL: <https://code.djangoproject.com/ticket/23406#comment:13>
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.f569bf18e99e768b24cb654999826b29%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to