Malcolm Tredinnick wrote: > On Wed, 2006-08-09 at 14:58 -0700, [EMAIL PROTECTED] wrote: > > I'm still a little concerned about efficiency, particularly importing > > Serial Number for every year. When I moved it to the top of the model > > it failed "cannot import name Year" maybe because of the foreignKey > > relationship? > > Python only imports each module once. The next time you issue the import > statement is checks to see if the name is in sys.modules and, if so, > does nothing. So having the import statement there costs you precisely > one dictionary key lookup each time. So, nothing at all, really.
...and it wouldn't be imported until you called that function, so it may save you memory or start-up time if you never call it. Doubt that matters on a long running django process (you're bound to call it some time), but worth knowing in general python land. This.... > If it helps any, I'm on dreamhost (and thus, fcgi), and it doesn't > error out quickly. It acts as though it's trying for a long time, then > fails. > > Also, I should have mentioned, this WAS working just fine, up until I > checked it today. Since I last checked it, both new years and serial > numbers have been added (quite a few serial numbers), and I updated > Django (yesterday). ...makes me think the underlying issue here was that the process was taking too long and you were hitting some kind of (dreamhost specific) processor time limit. It probably came into play because the database had become larger. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
