Why are signals not called events?

Question

From what I can tell, in Python and Django, signals are just delegated events. Is there anything that functionally distinguishes them from the typical concept of events in C #, Java, ActionScript, etc.

Answer 1

Actually, the “signals” were around longer than the events. In its earliest use, the signal was an asynchronous way for processes to receive notifications of events that occurred. Since Unix is ​​much older than Django (and since a lot of Django work came from the pydispatcher where the original materials were made), the name is stuck.

Events are really signals, you can tell!

Answer 2

Signals typically communicate with an operating system object, and events are typically determined by the application. In some technology packages, material at the OS level can be hidden enough that there is no difference in the API, but maybe not in others.

Answer 3

Afaik Qt had the first signal / slot implementation. Qt docs explain the metaphor: "A signal is emitted when a specific event occurs." The difference is so subtle that the nomenclature has been blurred.

Answer 4

You may also ask, “Why aren't events just called signals?” Differences in terminology occur.