Hi Brice, Thanks for the suggestion! I'm not sure whether if I can successfully implement a library like you've mentioned, so for now I might stick with the Watch* libraries available. I really love the goals you've listed and would add these to my proposal.
David Ma On Thursday, March 30, 2017 at 5:24:55 AM UTC-7, contact wrote: > > Hi David, > I think it's a good idea to improve what we have now, mostly for the > problems you described. > Don't you think it would be a better idea to make a reloader which > doesn't depend on Django at all? You could make a library working with a > settings file, and create a base settings file for Django projects. > You could define whatever should be called to start and restart the > server, and be able to define file types and folders that should be seen > as changes that require a restart or not. It could then be used easily > with any kind of Python project, and even allow specific behaviours, > like launching a server reload when a new plugin is uploaded to a > specific folder, or when one of them is updated. > Every Python framework could then embed their own base settings file, > which would allow this project to touch a wider audience. > > - Brice > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/f1194326-ed76-490f-999a-93cf6fc49890%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
