[Django]-Django 1.7 conflicting models

by

12👍

✅

Instead of importing the all project then the app then the module inside the app just import the app which is inside the project then the module.

Instead of 

from webproject.app import model

Use

from app import model

or

from app.models import Staffs
👤Wangolo Joel

5👍

I think this bug report (turns out it’s a feature) is related to your problem.

For me the problem was resolved by importing from resume.models only, rather than apps.resume.models. So search for "from apps." in your project and replace it.

(For me, removing __init__.py or changing the PYTHONPATH caused other problems, I imagine that’s common.)

👤Mark

0👍

This issue has a century, but here goes my solution that was really painful to find.
Given this project tree:

repo
├── app
│   ├── __init__.py
│   ├── project
│   │   ├── __init__.py
│   │   ├── asgi.py
│   │   ├── settings.py
│   │   ├── urls.py
│   │   ├── utils.py
│   │   └── wsgi.py
│   ├── core
│   │   ├── __init__.py
│   │   ├── admin
│   │   │   ├── __init__.py
│   │   │   └── ...
│   │   ├── apps.py
│   │   ├── models
│   │   │   ├── __init__.py
│   │   │   ├── mymodel.py
.   .   .   ...

Besides having the core folder included in the PYTHONPATH, there were places where I was doing from ..models import MyModel.

Apparently, using relative imports (..models) was in some way generating the path from the repo folder app, this is app.core.models.

When running the tests, it assumed a duplication through sometimes refering the the same model in both paths: <app.core.models.MyModel> and <core.models.MyModel>, so I opted for using core.models instead of ..models.

👤Federico Blanc

Leave a comment