django-stream provides activity streams for Django applications.
It differs from
django-activity-stream in that it does not use generic relations and does not provide a Follow object, but it can be used together with django-follow.
The motivation to not use generic relations is for simplicity reasons.
pip install django-stream- In your settings.pyadd stream types:
INSTALLED_APPS += ('stream', )
STREAM_VERBS = (
	('default', 'Stream Item'),
    ('edit', 'Object edited'),
    ('created','Object created'),
    ('deleted','Object deleted'),
    ('followed', 'Object followed'))- Register the models you want to be able to tag in your streams:
from django.db import models
from stream import utils
class MyModel(models.Model):
field = models.CharField(max_length = 255)
utils.register_actor(MyModel)
utils.register_target(MyModel)
utils.register_action_object(MyModel)Run tox.
$ git clone https://github.com/caffeinehit/django-stream.git && cd django-stream && tox
[...]The repository contains an example project and application making use
of django-stream in the test/ folder.
- 
ActionManager.create(actor, verb, target=None, action_object=None, **kwargs):
 Create a new action object
- 
ActionManager.get_or_create(actor, verb, target=None, action_object=None, **kwargs):
 Returns a tuple(Action, bool)
- 
ActionManager.get_for_actor(actor):
 Returns all theActionobjects involvingactor
- 
ActionManager.get_for_actors(actors):
 Similar to above, but acts on a list of actors
- 
ActionManager.get_for_target(target):
 Returns all theActionobjects involvingtarget
- 
ActionManager.get_for_targets(targets):
 Similar to above, but acts on a list of targets
- 
ActionManager.get_for_action_object(obj):
 Returns all theActionobjects involvingobj
- 
ActionManager.get_for_action_objects(objects):
 Similar to above, but acts on a list of action objects.
The generated fields on the Action model follow a simple pattern:
"%(field_prefix)s_%(model_name)s"Meaning, if you've registered the User model as actor target and as
action object, you could run custom queries like this:
Action.objects.filter(actor_user = User.objects.filter(username__startswith = 'a'))
Action.objects.filter(target_user = User.objects.filter(username__startswith = 'b'))
Action.objects.filter(action_object_user = User.objects.filter(username__startswith = 'c'))- 
stream.utils.register_actor(Model):
 MakeModela possible actor
- 
stream.utils.register_target(Model):
 MakeModela possible target
- 
stream.utils.register_acction_object(Model):
 MakeModela possible action_object
- 
stream.utils.action.send(actor, verb, target=None, action_object=None, description=None):
 Create a new action object
There is one template tag that attempts to render a given action:
{% load stream_tags %}
{% render_action action %}The template tag will try to find stream/<action.verb>.html and if it fails render the default template stream/action.html.
There is one signal that is fired when new actions are created:
stream.signals.action(instance)