I'm seeing the same error. It looks an awful lot like a bug, because the parameters don't line up to the ExceptionReporter:
def __init__(self, request, exc_type, exc_value, tb, is_email=False): It looks like *exc_info should contain the kwargs for exc_type, exc_value, and maybe tb, but it's assigned to exc_info = () if there is no stack trace available. I created a ticket (http://code.djangoproject.com/ticket/14972), but don't know enough about the logging design to determine if a patch goes in AdminEmailHandler or ExceptionReporter. I'll try to read through some of the logging design discussion, but I'm thinking I'll need some more feedback on this. This does seem to break the AdminEmailHandler functionality, which is critical for 1.3 release. -Ben On Dec 15, 4:36 pm, Adrián Ribao <ari...@gmail.com> wrote: > I get an error when using AdminEmailHandler. > > The error message is: __init__() takes at least 5 non-keyword > arguments (2 given) > > is in django/django/utils/log.py in emit line 90: > > reporter = ExceptionReporter(request, is_email=True, *exc_info) > > where exc_info = () > > Is it a bug or I'm missing something? > > Thank you, > > Adrian -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
