Earlier quoted context omitted.
> I have NEVER gotten that bug report. That's interesting, at my job we almost get these: we tend to dump tracebacks to the user, and it's common for them to screenshot the traceback (despite the "copy this error" button). Maybe you should have some sort of inline reporting interface à la Apple where the user can tell you what they were doing and provide contact info?
I get the same thing--or worse, screen shot pasted into a Word document that's attached to the email, so their two monitors are squished into 8.5 inches and any text is scaled down to illegibility. I also get a lot of near-misses, where they almost get it right: for example, copying the bit that says "there was an error, please include the information below when you report it" without actually copying the stack trace…
Yes I forgot to write that part in: while we rarely get the "screenshot pasted in word" (which IIRC stores the full image by default so you may be able to recover it, yay) the screenshotted traceback is usually cut off at the bottom, so we get the least useful part (wow I get the stack information of the WSGI handler, well that's going to be helpful) but commonly don't get the actually interesting part.
> It doesn't help matters that some of the software I inherited uses this antipattern: […]
Fuck everything about that with a rusty bonesaw.