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 and related discusions are partially >> obsolete compared to your current works, may I just know if your current >> evolution will automatically reproduce the auto init() of the devserver >> (i.e loading models from each installed app) ? Because being able to use >> the same several times, or to set its human name, are cool features, but >> imo the most critical part at the moment is that difference between dev and >> prod inits, which can bite hard the unwary djangoer. >> >> > The approach would be more along the lines of defining a place that is > guaranteed to run at as distinct a time as possible in the startup process > - rather than trying to guarantee that all code gets imported in some > coherent way with the aim to trigger module level import code. The latter > is what we want to move away from. > > -Preston > >
OK, I don't understand though in which cases one wouldn't want all his INSTALLED_APPS models to be imported at startup :? Some for the "coherent way" - doesn't python's import mechanism already ensure that modules depending on each other import themselves in a proper order (except if cyclic imports ofc) ? Regards, Pascal -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
