Could one options be to replace the current devserver with the one from Werkzeug? It already uses watchdog (similar to watchman) for monitoring file system events and is well maintained. With Django now allowing dependancies, this seems like something that doesn't necessarily need to be developed internally.
The Werkzeug devserver also has some niceties like an interactive debugger and ssl hosting with an automatically issued self signed certificate. It could be implemented behind the current management command relatively easily. There is already an implementation as part of django-extentions that I believe is well used and battle tested - http://django-extensions.readthedocs.io/en/latest/runserver_plus.html On Thursday, January 5, 2017 at 9:11:53 AM UTC, Aymeric Augustin wrote: > > On 4 Jan 2017, at 23:31, Bobby Mozumder <bmoz...@gmail.com <javascript:>> > wrote: > > > I guess I could just use Watchman to restart the Django development > server as needed? > > > If you find a way to tell watchman to run `django-admin runserver > --noreload` and restart it whenever a file in the current directory > changes, that should do the job. > > Unfortunately the APIs exposed by watchman don’t make this trivial. > They’re intended to run a build process that will terminate, while the > development server will keep running. > > -- > Aymeric. > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6d346a13-b096-42f8-a15b-a2814a81eef5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
