posativ/acrylamid — pull request #60 by markvl (2012-08-23 20:17:56+00:00)
Title: Implement tag feeds

In the branch I'd like to get merged, I created two views (``AtomPerTag`` and ``RssPerTag``) which can generate Atom and RSS feeds for all tags by including something like this in your ``conf.py``:

'/tag/:name/atom/': {'filters': ['h2', 'nohyphenate'], 'view': 'atompertag'},
'/tag/:name/rss/': {'filters': ['h2', 'nohyphenate'], 'view': 'rsspertag'},

First I changed the Feed views so the name of the view class does not determine which template is used (e7529416). Then I implemented the AtomPerTag and RssPerTag classes (d0f86164).
Finally I changed the way views are found in modules to make sure we can use ``atompertag`` in our configuration, instead of having to type ``AtomPerTag`` (c1da3351).

I'm not particularly proud of the way the feeds are implemented... For example the ``context`` method in ``FeedPerTag`` is almost a copy of the ``context`` method of the ``Tag`` view (minus the tag cloud stuff). I also do not like the duplication in ``Atom`` and ``AtomPerTag`` (and likewise ``RSS`` and ``RssPerTag``). In other words: it's not very DRY.

I can imagine if you don't want to merge this code as is. But if that is the case, could you please provide some pointers on a better way to solve this?