Easier chainability with custom QuerySets

Django allows you to specify your own ModelManager with custom methods. However, these methods are chainable. That is, if you have a method on your PersonManager caled men(), you can't do this:

Person.objects.filter(birth_date__year=1978).men()

Normally, this isn't a problem, however your app may be written to take advantage of the chainability of querysets. For example, you may have an API method which may return a filtered queryset. You would want to call with_counts() on an already filtered queryset.

In order to overcome this, we want to override django's QuerySet class, and then make the Manager use this custom class.

The only downside is that your functions will not be implemented on the manager itself, so you'd have to call Person.objects.all().men() instead of Person.objects.men(). To get around this you must also implement the methods on the Manager, which in turn call the custom QuerySet method.