#13903: Auto app_label creation fails when model is defined at top-level python
modules
--------------------------------------------------------+-------------------
Reporter: petraszd | Owner:
anonymous
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 |
--------------------------------------------------------+-------------------
Comment (by russellm):
app_label is a really nasty hack. Ideally, it wouldn't be required at all.
It was introduced as a workaround for certain nested model module
situations.
I don't think we should be encouraging it's use for situations like the
one you describe. To my mind, a model should belong to an app. If a model
isn't in an app, that's an error, and should be raised as such, early and
loudly.
--
Ticket URL: <http://code.djangoproject.com/ticket/13903#comment:6>
Django <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.
