Hi, I have created a branch at https://github.com/dracos/django/compare/pipe-cleaning that builds upon a previous patch posted to this list and outputs "Broken pipe" instead of a traceback for such an error. As the history below shows, practically speaking all reports of broken pipe tracebacks in the log are due to the browser cutting off output, and are not helpful to be shown as a full traceback. I get them frequently (e.g. hit refresh before your previous page has finished loading to sometimes get it), and find them annoying.
I am posting here because ticket #4444 - https://code.djangoproject.com/ticket/4444 - is marked wontfix. I am not "imagei" on that ticket, I just came across the ticket recently whilst trying to work out why my Selenium tests on Travis were failing with broken pipes when they were fine last week - https://github.com/travis-ci/travis-ci/issues/2610 (some change to underlying Travis, I assume). Ticket #4444 was opened in May 2007, and marked wontfix in September 2007 saying "The best we could is to have a more explicit error message." In 2008 someone provided a patch to make it a logged error message rather than spew a scary traceback, there was a +1 and a "leave as-is", then silence. There was a brief reopening of the thread in 2012 by two people who also found the broken pipe tracebacks tedious, then nothing further since then. The thread (2008 and 2012) can be found at https://groups.google.com/forum/#!topic/django-developers/W1Nns9k40EQ (The 'python manage.py runserver --help' is a little bit confusing because it has a --traceback argument and yet you still get a traceback - you have to have read the default options section of the django-admin.py documentation to know that only makes a difference to CommandError, not any other type of error. My branch also adds "CommandError" to the help output of --traceback.) The 2008 patch doesn't really work any more, but I think I've made the spirit of the same thing on the current Django code. I hope this can be considered for inclusion, as I think it tidies up a common issue with runserver output that will especially confuse people new to Django. Do let me know if I've gone about fixing it in the wrong way, or if I should do something differently. In my testing it certainly makes my runserver logs nicer to follow :) ATB, Matthew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/366d72ce-ce4f-4487-bbfd-a095d0c8c397%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
