Why not build in the most common approach while still allowing people to override it like they do know? They could simply swap out the default manager right?
On 06/13/2017 06:54 PM, James Bennett wrote: > Because even if you collapse the number of approaches to just two general > options, there's still enough variability in the specifics of how to > implement those options that there's no clear "one size fits all" solution > at the moment. If there ever is one, it can be considered for inclusion in > Django, but right now there just isn't. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/5d32decb-6468-21e0-0756-91fde47ab20b%40gmail.com. For more options, visit https://groups.google.com/d/optout.
