While trying to answer a question in the IRC channel today, I was poking around in the template system and noticed that resolve_variable has a comment about a particularly odd "gotcha": because it catches and silently hides a TypeError raised by calling a method without the appropriate number of arguments, it also ends up catching and silently hiding a TypeError raised by something going wrong within the method itself.
Out of curiosity, what's the reasoning for this? Would we incur a significant performance penalty by looking at the exception to see whether it's complaining about the number of arguments (in which case it should not propagate) or whether something else has gone wrong and raised a TypeError (in which case the exception probably should propagate and result in a 500 error)? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
