#7852: Cross-application model inheritence broken after newforms-admin merge
---------------------------------------+------------------------------------
Reporter: jbalonso | Owner: nobody
Status: new | Milestone:
Component: Database wrapper | Version: SVN
Resolution: | Keywords: model inheritance
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Comment (by jbalonso):
Replying to [comment:2 mtredinnick]:
> That proposed API is terrible. We are programming Python here and
subclassing has a well-established syntax. It looks like something about
the new admin code's importing needs to be fixed. Certainly "breaking"
Python isn't the solution here.
Very well. Then I suggest the API for registering models for the admin
interface either be taken out of models.py files entirely or wrapped in a
class so the registration code isn't run on every import.
I think any solution to this that will require a backwards-incompatible
API change. As such, I think this should be resolved by the 1.0 release.
Being a relatively rookie ticket submitter, I'm not going to set the
milestone myself, though.
--
Ticket URL: <http://code.djangoproject.com/ticket/7852#comment:3>
Django Code <http://code.djangoproject.com/>
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?hl=en
-~----------~----~----~----~------~----~------~--~---
