Opened 2 months ago

Closed 7 weeks ago

#36495 closed New feature (wontfix)

Template file changes do not trigger a server reload

Reported by: Dominika Owned by:
Component: Utilities Version: 5.2
Severity: Normal Keywords: templates, autoreload, watcher, filewatcher
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Change History (2)

comment:1 by David Sanders, 2 months ago

Component: UncategorizedUtilities

Thanks for the report, though a couple of things:

  • runserver doesn't need to be reloaded for a template change, templates should just be reread
  • the code you referred to seems counter-intuitive and confusing
  • out of curiosity, I removed the not and ran the test suite and it all passed

I think there may be some clarification that's required here, and possibly a test written (because any change to code should break a test somewhere, somehow) but I don't think any change is necessary from my first point above.

I believe what that is supposed to do is reload, only if there's a .py file in the templates directory, hence the return (None) when the filename ends with .py.

comment:2 by Sarah Boyce, 7 weeks ago

Resolution: wontfix
Status: newclosed
Summary: Bug in determining if template file should be autoreloaded in `django.utils.autoreload.notify_file_changed` ?Template file changes do not trigger a server reload
Type: BugNew feature

Given #32744, I don't believe this is desired behavior
Changes to behavior need to be proposed and discussed with the community. To do that, please raise this on the new feature tracker.

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