HTTPS clone URL
Subversion checkout URL
Library for Role based development
Fetching latest commit...
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Roles ===== Library for Role based development. Pythonic implementation of the DCI (Data Context Interaction) pattern (http://www.artima.com/articles/dci_vision.html). The big difference with mixins is that this role is applied only to the subject instance, not to the subject class (alas, a new class is constructed). Roles can be assigned and revoked. Multiple roles can be applied to an instance. Revocation can happen in any particular order. Homepage: http://amolenaar.github.com/roles Releases: http://pypi.python.org/pypi/roles Using Roles ----------- As a basic example, consider a domain class: >>> class Person(object): ... def __init__(self, name): ... self.name = name >>> person = Person("John") The instance should participate in a collaboration in which it fulfills a particular role: >>> from roles import RoleType >>> class Carpenter(object): ... __metaclass__ = RoleType ... def chop(self): ... return "chop, chop" Assign the role to the person: >>> Carpenter(person) # doctest: +ELLIPSIS <Person+Carpenter object at 0x...> >>> person # doctest: +ELLIPSIS <Person+Carpenter object at 0x...> The person is still a Person: >>> isinstance(person, Person) True ... and can do carpenter things: >>> person.chop() 'chop, chop' See `roles.py <http://github.com/amolenaar/roles/blob/master/roles.py>`_ for more examples. Context ------- Roles make a lot of sense when used in a context. A classic example is the money transfer example. Here two accounts are used and an amount of money is transfered from one account to the other. So, one account playes the role of source account and the other plays the role of target account. An example can be found in `example.py <http://github.com/amolenaar/roles/blob/master/example.py>`_ and `example2.py <http://github.com/amolenaar/roles/blob/master/example2.py>`_.