Fixed a bug with related object fetching.

Author: debrouwere

README

@@ -1,6 +1,6 @@
 What the heck is this?
 ----------------------
 
-There are a lot of versioning apps out there, either in a state of decrepitude, or functional but with a colvoluted or suboptimal design. This app intends to become the de-facto standard to manage revisions in Django.
+There are a lot of Django versioning apps out there, either in a state of decrepitude, or functional but with a colvoluted or suboptimal design. This app intends to become the de-facto standard to manage revisions in Django.
 
-But not quite yet. Because it's more alpha than alpha and it has failing tests. Just so y'know. You can run the tests yourself with python revisions/tests/testrunner.py
+Recently crawled out of alpha and has a good test suite, but it's not quite production-grade. Just so y'know.

docs/index.rst

@@ -1,5 +1,5 @@
 =============================================
-Welcome to django-versioning's documentation!
+Welcome to  django-versioning's documentation!
 =============================================
 
 Contents:

docs/roadmap.rst

@@ -80,7 +80,6 @@ def revert_to(self, criterion):
             revert_to_obj.save()
             return revert_to_obj
 
-    
     def get_latest_revision(self):
         return self.get_revisions().order_by('-vid')[0]
 
@@ -119,9 +118,9 @@ def _get_related_objects(self, relatedmanager):
         # kind of convoluted deep dive into the internals of the related class.
         #
         # By all means, I'd welcome suggestions for prettier code.
-        
         ref_name = self._meta._name_map[related_model_name][0].field.name
-        objs = related_model._default_manager.filter(**{ref_name + '__in': self.get_revisions()})
+        pks = [story.pk for story in self.get_revisions()]        
+        objs = related_model._default_manager.filter(**{ref_name + '__in': pks})
 
         return objs