#24875: inotify broken with vim, dev server does not restart
--------------------------------------------+--------------------
Reporter: chrisbainbridge | Owner: nobody
Type: Bug | Status: new
Component: Core (Management commands) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 1 | UI/UX: 0
--------------------------------------------+--------------------
Commit 15f82c7 ("used pyinotify as change detection system when
available") introduced a regression where editing a file in vim with
default settings (writebackup=auto) would no longer cause the dev server
to be restarted. On a write, vim moves the monitored file to a backup
path, and then creating a new file in the original. The new file is not
monitored as it has a different inode. Fix this by also watching for
inotify events IN_DELETE_SELF and IN_MOVE_SELF.
--
Ticket URL: <https://code.djangoproject.com/ticket/24875>
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/058.59ea8fba2fa7596548cdae4fa6bbc684%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
