Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1686 closed defect (duplicate)

Relative model import should work within app directory

Reported by: James Bennett Owned by: Adrian Holovaty
Component: Core (Other) Version: magic-removal
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


Assume a project with an application called 'weblog', whose models live in the directory weblog/, and with a model class called 'Entry'.

From within the top-level directory for the project, doing 'from weblog.models import Entry' works as expected.

From within the 'weblog' directory, doing 'from models import Entry' should work, but instead produces this traceback:

Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "", line 17, in ?
    class Category(models.Model):
  File "/Users/jbennett/dev/092/magic-removal/django/db/models/", line 45, in __new__
    new_class._meta.app_label = model_module.__name__.split('.')[-2]
IndexError: list index out of range

It'd be nice if Django could handle this situation, as it makes app-specific URL configuration ever so much nicer (e.g., model imports to get QuerySets for generic views won't need the full path to the model, and hence won't be coupled to the project).

Attachments (1)

base.diff (766 bytes) - added by erob@… 13 years ago.
partial work-around: works with unittest and django.db.models.Model

Download all attachments as: .zip

Change History (3)

comment:1 Changed 13 years ago by James Bennett

Component: Admin interfaceCore framework

comment:2 Changed 13 years ago by Adrian Holovaty

Resolution: duplicate
Status: newclosed

Duplicate of #1658.

Changed 13 years ago by erob@…

Attachment: base.diff added

partial work-around: works with unittest and django.db.models.Model

Note: See TracTickets for help on using tickets.
Back to Top