#27543: AttributeError: '_Frame' object has no attribute 'f_back' / Django and
celery error logging gone wrong
-------------------------------------+-------------------------------------
Reporter: Simon Chenard | Owner: (none)
Type: Bug | Status: closed
Component: Error reporting | Version: 1.10
Severity: Normal | Resolution: needsinfo
Keywords: celery logging | Triage Stage:
traceback | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Chenard):
In the end I couldn't completely understand the relationship between
django and celery - but since it does only happens when celery is
involved, it's most likely not a issue on Django's side.
But for the record, if anyone else stumble on a similar case, what I did
end up doing is sub-classing the AdminEmailHandler and use python's own
traceback library, if the exception described earlier is raised.
--
Ticket URL: <https://code.djangoproject.com/ticket/27543#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.88a2b80850f01bd0f41d4fd3cd16d4ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
