Re: broken pipe issue with runserver #4444

On 18 joulu, 19:56, Julien Phalip wrote: > On Dec 18, 2012, at 5:18 AM, Emil Stenström wrote: > > > On Monday, 2 June 2008 02:45:07 UTC+2, Ludvig Ericson wrote: > > I'd rather see this be leaved as-is, since I haven't seen a single > > report on these broken pipe

Re: broken pipe issue with runserver #4444

On Dec 18, 2012, at 5:18 AM, Emil Stenström wrote: > On Monday, 2 June 2008 02:45:07 UTC+2, Ludvig Ericson wrote: > I'd rather see this be leaved as-is, since I haven't seen a single > report on these broken pipe 'issues'. > > Here's a report: > > I'm using PhantomJS (headless

Re: broken pipe issue with runserver #4444

On Monday, 2 June 2008 02:45:07 UTC+2, Ludvig Ericson wrote: > > I'd rather see this be leaved as-is, since I haven't seen a single > > report on these broken pipe 'issues'. > Here's a report: I'm using PhantomJS (headless webkit browser) to test for javascript errors on my site. Using the

Re: broken pipe issue with runserver #4444

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I'm +1 on this. An exception should only appear on the console if > something serious is broken. The term you're looking for is "error", not exception. An exception can be expected. Where would you fellows suggest we catch this exception, and

Re: broken pipe issue with runserver #4444

I'm +1 on this. An exception should only appear on the console if something serious is broken. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: broken pipe issue with runserver #4444

No it's not really a problem, thats why i called it an 'issue' between quotes :) It's probably better called something like a style issue. But some people see this as an problem, cause you get a loud (perhaps for some scarry) looking exception. For something which is essentially a non-problem.

Re: broken pipe issue with runserver #4444

While writing a little patch to get rid of the (annoyingly loud) 'broken pipe' exception/traceback; i found that there actually a ticket for it # which is marked won't fix. Is it really a problem at all? Ludvig "toxik" Ericson [EMAIL PROTECTED]

broken pipe issue with runserver #4444

Hi guys, While writing a little patch to get rid of the (annoyingly loud) 'broken pipe' exception/traceback; i found that there actually a ticket for it # which is marked won't fix. I would like to throw in two options for making this error a little less noisy. (As this error is 'common