Hi Rick,

On 11/18/2014 11:59 AM, Rick van Hattem wrote:
[snip]
> In all but the most basic Django projects I've seen problems like these.
> Sane defaults won't hurt anyone and solves issues for people with larger
> systems. And running forks of Django seems counter productive as well.

As a side note -- I'm not sure why running a fork of Django should be
necessary. All the suggestions you've made so far in this thread could
be implemented in a custom QuerySet subclass, and custom QuerySet
classes can be hooked into your models via a custom Manager (which can
even be created for you by Manager.from_queryset). Create an abstract
base Model using this Manager, inherit all your models from it, and you
can get the behaviors you want throughout your system without forking
Django.

Carl

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to