You might want to throw some logging into your application (Python's logging module). [0] If you use logging, you'll be able to get a better handle on where the problem is actually happening.
I've heard of the dev server crashing ungracefully when it encounters an error, but have never seen it myself. The reports I've heard all end up being programmer error, not problems with Django. Also, I've never heard of it taking down the whole machine. - Ben [0] http://docs.python.org/lib/node407.html -- the second example writes to a file On 3/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > On Mar 19, 1:56 am, "[EMAIL PROTECTED]" > <[EMAIL PROTECTED]> wrote: > > > The PC literally starts beeping like mad (it's a hardware beep that > > > you can hear even if the speakers are off). > > > > I know this is going to sound like a cop-out, but it really sounds > > like a hardware problem. There is no reason why a python script of ANY > > kind would cause a hardware lockup as you are describing. It sounds > > more like a memory fault. If it happens with more than one machine I > > would be extremely impressed. > > It _does_ happen on more than one machine and on both WinXp and > Win2k3. They're both Dell machines though with different hardware > > L. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
