testing with a mock object

i have a questions about mock objects. i currently have a django view function that calls a 2nd function. this second function calls urllib2.urlopen. i was thinking about adding in a mock object so i can get some better code coverage in the 2nd function when calling manage.py test. my first

Re: touching wsgi file

thanks for your detailed explanation. i had to read it 3 times to try to absorb everything :) i do not need to have the code be portable beyond mod_wsgi. if i'm following what you and steve have said and pages you both pointed me to, it appears if i want to share global data i really need to

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

Re: touching wsgi file

lume sites under apache child processes in linux. maybe this is not the recommended way it's done. On Nov 2, 2:17 pm, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > On Nov 3, 7:09 am, belred <[EMAIL PROTECTED]> wrote: > > > is touchingt the wsgi file supposed reload every

touching wsgi file

is touchingt the wsgi file supposed reload every file in the the entire django project or just just reload the one wsgi file? thanks, bryan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To

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

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

django signals

i'm having touble finding documention about django signals that explain how they behave under apache child processes. if i have a signal go off and have a listener for that signal. will only the listener in same child process receive it or will that same listener in all apache child processes