-----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 do nothing? Because that's half of the problem: there's no suitable place for it. From the HTTP-to&from-WSGI layer seen, a broken pipe is serious business. From the view's view (tee-hee), it won't ever matter. From the users' view, it all depends. I'd also like to duly note that these broken pipes can be errors - a misbehaving browser, perchance. Or maybe even Python's socketing gone wrong! I'd rather see this be leaved as-is, since I haven't seen a single report on these broken pipe 'issues'. Ludvig "toxik" Ericson [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkhDQpMACgkQXnZ94Kd6KafmLQCggNZcpjucwTL/vHztq44AqgDa SqkAn2+S17lvVQ4NxLqienrNtQKNh8sw =k3vX -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
