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

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

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

(contrib.admin) Improving object deletion

Hi all. Sometimes there is huge amount of related objects. In the effect there is no possibility to delete a model because of http timeout error. Displaying objects to be deleted is quite nice feature, but just unusable in cases like that. Another thing is that nobody will read 74k related

Re: (contrib.admin) Improving object deletion

Here is a ticket about the memory issue: https://code.djangoproject.com/ticket/10919 It's hard for me to evaluate the other idea without looking at the code. If you want to open a ticket and provide a patch, go ahead. On Friday, October 14, 2016 at 9:08:16 AM UTC-4, Marcin Nowak wrote: > > Hi

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

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: (contrib.admin) Improving object deletion

Marcin Nowak skrev: (14 oktober 2016 15:08:15 CEST) >Hi all. > >Sometimes there is huge amount of related objects. In the effect there >is >no possibility to delete a model because of http timeout error. >Displaying objects to be deleted is quite nice feature, but just

Re: (contrib.admin) Improving object deletion

On the same topic (I'm not really sure whether it's not the same thing you're talking about), currently, even if a user has not the permission to delete an object via the change form (because of some custom logic in modeladmin.has_delete_permission(request,obj) ), he can delete it via the batch