Re: sharing a module level variable

On Nov 3, 11:53 am, belred <[EMAIL PROTECTED]> wrote: > On Nov 2, 2:58 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > > > On Nov 3, 2:03 am, belred <[EMAIL PROTECTED]> wrote: > > > > On Nov 2, 3:29 am, Steve Holden <[EMAIL PROTECTED]> wrote: > > > > > belred wrote: > > > > > i have an

Re: sharing a module level variable

On Nov 2, 2:58 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Nov 3, 2:03 am, belred <[EMAIL PROTECTED]> wrote: > > > > > On Nov 2, 3:29 am, Steve Holden <[EMAIL PROTECTED]> wrote: > > > > belred wrote: > > > > i have an wget event in a cron job.  the view does some processing > > > >

Re: sharing a module level variable

On Nov 3, 2:03 am, belred <[EMAIL PROTECTED]> wrote: > On Nov 2, 3:29 am, Steve Holden <[EMAIL PROTECTED]> wrote: > > > > > belred wrote: > > > i have an wget event in a cron job.  the view does some processing > > > which involves calling external websites and databases (takes about 25 > > >

Re: sharing a module level variable

On Nov 2, 3:29 am, Steve Holden <[EMAIL PROTECTED]> wrote: > belred wrote: > > i have an wget event in a cron job.  the view does some processing > > which involves calling external websites and databases (takes about 25 > > seconds) and updates some module level dictionary lookup variables > >

Re: sharing a module level variable

belred wrote: > i have an wget event in a cron job. the view does some processing > which involves calling external websites and databases (takes about 25 > seconds) and updates some module level dictionary lookup variables > (about 7 MB of data) which the rest of the program reads. but >

sharing a module level variable

i have an wget event in a cron job. the view does some processing which involves calling external websites and databases (takes about 25 seconds) and updates some module level dictionary lookup variables (about 7 MB of data) which the rest of the program reads. but unfortunately, only the one