/usr/share/doc/python-louie/doc/about.txt is in python-louie 1.1-2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 | =======
About
=======
Louie is based on PyDispatcher_. Here is a very good detailed
description of what both PyDispatcher and Louie offer you, based on
the description available at the PyDispatcher website.
.. _PyDispatcher: http://pydispatcher.sf.net/
.. sectnum::
.. contents::
PyDispatcher provides a multiple-producer-multiple-consumer
signal-registration and routing infrastructure, suitable for use in
multiple contexts.
The dispatcher mechanism is particularly useful when constructing
Model-View-Controller style applications where it is not desirable to
have the Model objects aware of the event model.
To be more concrete about what PyDispatcher does for you, here are
some specifics:
* A centralized service delivers messages to registered objects in the
local process. You can register any number of functions or other
callable objects which can receive signals from senders.
- Registration can be for any sender, particular sending objects, or
"anonymous" messages (messages where the sender is None).
- Registration can be for all signals, or particular signals.
- A single signal will be delivered to all appropriate registered
receivers, so that multiple registrations do not interfere with
each other.
- The sender or receiver need not be be dispatcher-aware. Any
Python object, except for `None`, can act as a sender, and any
callable object can act as a receiver.
- The system uses weak references to receivers wherever possible.
- Object lifetimes are not affected by PyDispatcher registrations.
When your object goes away, the registrations related to the
object also go away.
- References to common transient objects (instance methods in
particular) are stored as compound weak references.
- Weak references can be disabled on a registration-by-registration
basis.
* It allows rich signal types. Signals must simply be hashable
objects; they are otherwise opaque to the dispatch mechanism.
* Positional and keyword arguments may be attached to a signal when
sending. For each receiver, PyDispatcher sends each receiver the
arguments that they expect; other arguments are silently dropped.
Thus, receivers can be general in nature, even ignoring all
arguments, or they can be specific, accepting whichever arguments it
needs.
..
Local Variables:
mode: rst
End:
|