Re: The threat of the incompletely initialized django instance

2013-04-20 Thread Pakal
On Tuesday, April 16, 2013 8:41:26 AM UTC+2, ptone wrote: > > > > On Monday, April 15, 2013 4:51:24 AM UTC-7, Pakal wrote: >> >> (my previous answer disappeared in googlemail, I hope that one will >> survive the sending...) >> >> Thanks for the feedback, >> >> Preston, since ticket #3591 ticket

Re: The threat of the incompletely initialized django instance

2013-04-15 Thread ptone
On Monday, April 15, 2013 4:51:24 AM UTC-7, Pakal wrote: > > (my previous answer disappeared in googlemail, I hope that one will > survive the sending...) > > Thanks for the feedback, > > Preston, since ticket #3591 ticket and related discusions are partially > obsolete compared to your current

Re: The threat of the incompletely initialized django instance

2013-04-15 Thread Pakal
(my previous answer disappeared in googlemail, I hope that one will survive the sending...) Thanks for the feedback, Preston, since ticket #3591 ticket and related discusions are partially obsolete compared to your current works, may I just know if your current evolution will automatically rep

Re: The threat of the incompletely initialized django instance

2013-04-14 Thread ptone
On Saturday, April 13, 2013 5:03:16 PM UTC-7, Russell Keith-Magee wrote: > > > On Sat, Apr 13, 2013 at 11:53 PM, Pakal > > wrote: > >> Hello, >> >> since version 1.2, there has been no changes about this issue, which >> still bothers me: >> https://code.djangoproject.com/ticket/14916 >> >> In s

Re: The threat of the incompletely initialized django instance

2013-04-13 Thread Russell Keith-Magee
On Sat, Apr 13, 2013 at 11:53 PM, Pakal wrote: > Hello, > > since version 1.2, there has been no changes about this issue, which still > bothers me: > https://code.djangoproject.com/ticket/14916 > > In summary, the django dev server loads models.py of every INSTALLED_APP, > and thus (somehow) ens