#1836: Decouple Admin inner class from Model
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: low | Milestone:
Component: Metasystem | Version:
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by ubernostrum):
I don't really see it as an issue of decoupling -- the contents of the
administrative interface for a model ''should'' be coupled to the
definition of that model. I do see this proposal raising problems with
DRY, however, because it would mean that the model definition would no
longer be the single place for obtaining information about the model.
--
Ticket URL: <http://code.djangoproject.com/ticket/1836>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
