Removed all references to Model.objects, replaced by Model._default_manager.
fix: python syntax error (annoying when precompiling all py)
Evaluating a queryset in a boolean context causes is to generate a query
Fixed issue with select_related on proxy models: get_field_by_name result interpretation was incorrect
Merge pull request #160 from spectras/boolean_qs_glitch_fix

Check is queryset is none, instead of evaluating it
Merge pull request #159 from webu/bug/test_utils_python_syntax_error

fix: python syntax error (annoying when precompiling all py)
Added test case for select_related on proxies
Include documentation in source distribution.
Merge pull request #163 from fladi/include_docs

Include documentation in source distribution.
Merge pull request #162 from spectras/select_related_fix

Fix: select_related on proxy models fails: get_field_by_name result interpretation is incorrect
Merge pull request #145 from spectras/defaultmanager_fix

Fix: Removed all references to Model.objects, replaced by _default_manager
Merge pull request #151 from aptivate/ticket_141

This looks good, thanks!
Fixed fieldtranslator logic for getting next model. Now also works with foreign keys in proxy models.
Added a test case for this specific issue.
Updated django versions we test against
Merge pull request #144 from spectras/fieldtranslator_fix

Fix: Fieldtranslator fails on proxy model related fields as get_field_by_name's result interpretation was incorrect
Fix issue #140: _recurse_q crashes when actually recursing. It now properly keeps track of returned new_q's and longjoins.
Merge pull request #164 from spectras/django_version_updates

Updated django versions we test against
Merge pull request #153 from spectras/aware_recurse_q_fix

Fix issue #140: TranslationAwareManager's _recurse_q crashes when actually recursing.
Link each all_translation entry to the corresponding admin page

This makes a better user experience.
Updates tests and documentation.
Django 1.6 renamed get_query_set functions to get_queryset.