#22991: Development server not reloading with *.pyc files and without inotify
-------------------------------------+-------------------------------------
     Reporter:  lorinkoz@…           |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Core (Management     |                  Version:  1.7-rc-1
  commands)                          |               Resolution:
     Severity:  Release blocker      |             Triage Stage:  Accepted
     Keywords:                       |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  1                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by CollinAnderson):

 * needs_tests:  0 => 1


Comment:

 *.pyc filenames are ending up in `_cached_filenames`, and then being
 returned from the cache without being converted from `.pyc` to `.py`. This
 change caches the `*.py` filenames instead.
 https://github.com/django/django/pull/2913

 I also noticed an inconsistency with `_error_files`. It's not clear if or
 when those should be added to _cached_filenames and if and when inotify
 needs to start watching them.

 I would appreciate someone else writing a test case.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/22991#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.33a526eca11c17907c0a4c21d275f4a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to