Am Mittwoch, 17. Juli 2013 10:20:47 UTC+2 schrieb Russell Keith-Magee: > > > On Mon, Jul 15, 2013 at 8:17 PM, Christopher Medrela > <[email protected]<javascript:> > > wrote: > >> Progress: I've implemented manager checks. >> >> This API allows us to register, among other things, app-specific checks. >> But >> it's not necessary to write an app in order to do some checks. >> >> `register` function will have two optional parameters: `run_in_production` >> (default: False) and `run_in_development` (default: True) that let you >> specify >> when the callable should be called. Most checks should be performed only >> in >> development environment (which is equivalent to DEBUG==True). Security >> checks >> makes sense only in production environment (<==> DEBUG==False). >> >> I would be happy if I could hear your opinion! >> > > Hi everyone,
just out of curiosity (excuse me if I am wrong): Isn't there already a strong determing factor of whether a django project is running "in development" or "in production" despite the debug setting? In development you would usually use manage.py to invoke your devserver. But in production the entry point is the wsgi.py file, isn't it? At least this seems to be a more reliable approach for me than the pure differentiation based on the state of the debug setting. Simon -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
