James Bennett wrote:
> My personal preference would be to specify an interface that comments
> have to implement, and then let the actual model be whatever the
> developer wants; maybe a subclass of django.contib.models.Comment,
> maybe not. That feels like it'd give the maximum flexibility, and also
> feels a bit more natural in terms of Python -- rather than having to
> *be* a Comment, it just has to be able to *act like* a Comment.

+1


--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to