So, I'm trying to grok Python, and I'm doing a fairly good job at it, but I just want to make sure I'm not missing something.

In VB/C#/Java, there is the concept of the "Raised Event" - an event within an object that triggers an external function, without ending the object itself as a raised exception would. You can simulate something like this by the external creator assigning a function to a property in the object, and perhaps this is the way it is intended to be done in Python.

Am I correct, or has my rapid pace through the tutorials I have read made me miss something? Is there a reason that the "Raised Event" model of programming in Java/C#/VB inherently Evil (other than the fact that 2 of the 3 are M$ languages, and the third is Java) or is this just something that the Python Powers That Be decided not to implement?

Hope that made sense...

I haven't used 'raise event'--is that just a glorified callback?

Something like that. Quoting from the C# language specification, 1.7.5 Events:

An event is a member that enables an object or class to provide notifications. A class defines an event by providing an event declaration, which resembles a field declaration, though with an added event keyword, and an optional set of event accessors. The type of this declaration must be a delegate type.

An instance of a delegate type encapsulates one or more callable entities. For instance methods, a callable entity consists of an instance and a method on that instance. For static methods, a callable entity consists of just a method. Given a delegate instance and an appropriate set of arguments, one can invoke all of that delegate instance\ufffds methods with that set of arguments.

Just was wondering if I saw the way it's supposed to be done, or if I was missing it. In Python, it looks like you add a function to the list of functions for that event. When the "event" triggers, you walk through the list of functions, and call them.