#23882: django 1.7 + inotify breaks autoreload of runserver with vim
------------------------------+------------------------------------
Reporter: orzel | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.7
Severity: Normal | Resolution:
Keywords: autoreload | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"b252e0f35076c0585496b50ad1361ca419059104" b252e0f]:
{{{
#!CommitTicketReference repository=""
revision="b252e0f35076c0585496b50ad1361ca419059104"
[1.8.x] Refs #23882 -- Added detection for moved files when using inotify
polling
Commit 15f82c7 ("used pyinotify as change detection system when
available") introduced a regression where editing a file in vim with
default settings (writebackup=auto) no longer causes the dev server
to be restarted. On a write, vim moves the monitored file to a backup
path and then creates a new file in the original. The new file is not
monitored as it has a different inode. Fixed this by also watching for
inotify events IN_DELETE_SELF and IN_MOVE_SELF.
Backport of e5cfa394d79b6ab1b412bd3b30c6a433b415d56b from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23882#comment:12>
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/063.d696c64950e2fb493ce18b2939a2600b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
