Re: Changing development server threads type.

Thank you all for the feedback and thanks Tim for the merge. I'm very interested in the idea of integrating with Gunicorn. We can take things slowly with that integration (starting as suggested with just an option to use Gunicorn with runserver command), and limit modifying the current server

Re: Changing development server threads type.

On Wednesday, 4 June 2014 17:41:53 UTC+1, Ramiro Morales wrote: > > For this particular change I'd go with what Moayad proposes but > without the backward compatibility command line switch (assuming it > actually enhance the reloadind responsiveness). > > > I've tried the 1-liner version here

Re: Changing development server threads type.

On Wed, Jun 4, 2014 at 11:29 AM, Tim Graham wrote: > I think we should try to move away from maintaining our own web server and > focus our efforts on trying to integration with others like gunicorn > (#21978). For this particular change I'd go with what Moayad proposes but

Re: Changing development server threads type.

I think we should try to move away from maintaining our own web server and focus our efforts on trying to integration with others like gunicorn (#21978 ). On Tuesday, June 3, 2014 12:43:19 AM UTC-4, Moayad Mardini wrote: > > Hi, > > The development

Changing development server threads type.

Hi, The development server currently uses "non-daemon threads" for the socketserver, this has many bad side effects, as discussed in ticket #21773 ( https://code.djangoproject.com/ticket/21773 ). The most annoying disadvantages of that are: 1) Longer time to restart, because the sever has to