Opened 18 years ago

Closed 15 years ago

#5048 closed (wontfix)

Allow TypeError exceptions to propagate in templates

Reported by: Jan Rademaker <j.rademaker@…> Owned by: nobody
Component: Template system Version: dev
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

This patch fixes a gotcha by counting the number of entries in the traceback. More than 1 entry means the exception happened somewhere in the method.

Attachments (1)

ticket5048.diff​ (2.7 KB ) - added by Jan Rademaker <j.rademaker@…> 18 years ago.

Download all attachments as: .zip

Change History (5)

by Jan Rademaker <j.rademaker@…>, 18 years ago

Attachment: ticket5048.diff​ added

comment:1 by Simon G. <dev@…>, 18 years ago

Triage Stage: Unreviewed → Ready for checkin

comment:2 by Adrian Holovaty, 18 years ago

Triage Stage: Ready for checkin → Design decision needed

Wait -- we don't want TypeError to be propogated. One of the design goals for the template system is that it shouldn't propogate exceptions.

in reply to:  2 comment:3 by Jan Rademaker <j.rademaker@…>, 18 years ago

Replying to adrian:

Wait -- we don't want TypeError to be propogated. One of the design goals for the template system is that it shouldn't propogate exceptions.

Are you talking about the current sitution or how you think it ought to be? Because right now, any Exception is propogated, except TypeErrors (due to the gotcha) and exceptions with a silent_variable_failure attribute set to True.

comment:4 by Malcolm Tredinnick, 15 years ago

Resolution: → wontfix
Status: new → closed

This is backwards incompatible and we really prefer template rendering to never be replaced with a 500 page due to internal crashes time.

Note: See TracTickets for help on using tickets.
Back to Top