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. I'm all for not fixing every little quirck browsers throw at us, but this could be a very very simple patch which will stop the console being littered with useless exceptions when using runserver. It just feels wrong IMHO to have exceptions raised for users where the reaction too questions about it will be: 'just ignore it completely, it's a browser issue'. - Ido On Sun, 2008-06-01 at 10:49 +0200, Ludvig Ericson wrote: > > 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 > > #4444 which is marked won't fix. > > Is it really a problem at all? > > > Ludvig "toxik" Ericson > [EMAIL PROTECTED] > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
