Context Navigation

Changes between Initial Version and Version 1 of Ticket #19866, comment 23

initial	v1
1		One of the problematic things about the use of SuspiciousOperation, is that there is no way to get any specificity of event types. If you care about some more than others, it you're stuck with parsing strings.
	1	One of the problematic things about the use of SuspiciousOperation, is that there is no way to get any specificity of event types. If you care about some more than others, you're stuck with parsing strings.
2	2
3	3	Since we only raise this exception in relatively few places (I think I count 8), one idea would be to subclass SuspiciousOperation for each case, and have the logger put in e.__name__ at the beginning of the message, so there would at least be that.