On 04/04/2012, at 8:44 PM, Tai Lee wrote:

> I'm not so sure that it's necessary or even desirable to solve the "general" 
> problem of swappable models. If anyone can swap any model by changing a 
> setting, that sounds like a recipe for confusion to me.

Sure, but that's not what I've proposed. A model would only be swappable if the 
original app developer declared that model as swappable. An end user wouldn't 
be able to arbitrarily decide that they wanted to replace a model in an app 
developed by someone else.

And sure, any feature we add could ultimately end up being used (and overused) 
in bad ways. However, that's true of any language or library feature. Classes, 
metaclasses, decorators, or any other Python language feature can be both used 
and abused, as can Django features like ModelForms or the internals of the Meta 
class. 

My point is that there is nothing about this problem that is unique to User. 
Django's own codebase contains another example of exactly the same pattern -- 
Comments. Therefore, we shouldn't pretend that the solution is User specific. 
At some point, we have to just provide enough documentation and guidance to 
shepherd people away from bad architectural decisions, and trust that the 
userbase will take that advice.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to