Opened 6 years ago

Last modified 5 years ago

#30479 closed Bug

Autoreloader with StatReloader doesn't track changes in manage.py. — at Version 1

Reported by: Keryn Knight Owned by: nobody
Component: Utilities Version: 2.2
Severity: Release blocker Keywords: autoreload
Cc: Tom Forbes Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Mariusz Felisiak)

This is a bit convoluted, but here we go.

Environment (OSX 10.11):

$ python -V
Python 3.6.2
$ pip -V
pip 19.1.1
$ pip install Django==2.2.1

Steps to reproduce:

  • Run a server python manage.py runserver
  • Edit the manage.py file, e.g. add print(): 
    def main():
    print('sth')
    os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'ticket_30479.settings')
    ...

Under 2.1.8 (and prior), this will trigger the auto-reloading mechanism. Under 2.2.1, it won't. As far as I can tell from the django.utils.autoreload log lines, it never sees the manage.py itself.

Change History (1)

comment:1 by Mariusz Felisiak, 6 years ago

Cc: Tom Forbes added
Component: Core (Management commands) → Utilities
Description: modified (diff)
Severity: Normal → Release blocker
Summary: Auto-reloading with StatReloader may not track changes to the main entrypoint? → Autoreloader with StatReloader doesn't track changes in manage.py.
Triage Stage: Unreviewed → Accepted

Thanks for the report. I simplified scenario.

Regression in c8720e7696ca41f3262d5369365cc1bd72a216ca.
Reproduced at 8d010f39869f107820421631111417298d1c5bb9.

Note: See TracTickets for help on using tickets.
Back to Top