Re: Please put monitor.py as default in next django version

Hello, On 15 Oct 2016, at 02:40, Curtis Maloney wrote: > > What sort of situations are you seeing that you want a restart frequently and > more simple than "touch wsgi.py" ? Developing locally with Apache is a common use case, but mod_wsgi handles this:

Re: Please put monitor.py as default in next django version

On 15/10/16 08:16, Ricardo Prado wrote: Thanks "Folks" in special Aymeric Let's go, let me explain about this "monitor.py". When users deploy django app in production, the changes in any python script need be "reloaded" for apply changes, in this you have two options to do this: 1 - restart

Re: Please put monitor.py as default in next django version

Hello, I agree with Florian. Deployments are not the same across the board. It is also simple enough to write something like a fabric script that handles your own unique process accordingly. This would make an excellent additional package on pypi, but I do not see a reason to include it as a

Re: Please put monitor.py as default in next django version

Hi, On Saturday, October 15, 2016 at 1:38:32 AM UTC+2, Ricardo Prado wrote: > > An internal montior is initialized for apply changes runtime. Would be > good have this option in production too. > I tend to disagree. Having this in production would be kind of bad -- it takes extra resources and

Re: Please put monitor.py as default in next django version

Thanks "Folks" in special Aymeric Let's go, let me explain about this "monitor.py". When users deploy django app in production, the changes in any python script need be "reloaded" for apply changes, in this you have two options to do this: 1 - restart apache or nginx server 2 - "touch

Re: Please put monitor.py as default in next django version

Hello Ricardo, I looked for monitor.py but I’m not sure what you’re referring to. I don’t know what you call the “dev tools” either; If you’re thinking of the debug toolbar it’s a third party project. To move forwards with this, you’ll have to