What's the suggested way of importing modules within a django project

Question

This has always bothered me, and I've never really come up with my own preferred way of doing this.

When importing something from one of your own applications in a django project, do you import with:

from myproject.mymodule.model import SomeModel from myproject.anotherone.model import AnotherModel

or, do you do:

from mymodule.model imoprt SomeModel from anotherone.model import AnotherModel

Of course, either will work as long as you set your PYTHONPATH correctly when deploying. Even a combination of the two within a given project will work.

My issue with the second form is when you have a utils.py or the like sitting in the your project.

# This feels wrong import utils

But, that could just be me.

Which one is better and why?

Gabriel · Accepted Answer · 2015-10-12 13:25:39Z

I would recommend using the second alternative:

from mymodule.model import SomeModel from anotherone.model import AnotherModel

In Django, it's recommended to write reusable applications, that you may deploy in multiple projects. Specifying the name of the project would hinder this possibility. It would even complicate the case where you simply change the name of the top project folder!

This is the tradition that most django applications use (e.g. pinax, django contrib, etc).

For more details, you should listen to DjangoCon 2008: Reusable Apps.

LeafStorm · Accepted Answer · 2010-01-06 03:28:44Z

I prefer to use absolute imports whenever possible. The first reason is that relative imports are on their way out in Python 3, so it's best not to get into that habit. (Based on the way you phrased the question, I'm assuming that you put the application packages inside your project package.) The second reason is that it makes the intent of what you're importing more explicit.

Though my absolute best practice is to not put my application packages inside the project package. That way, it's easier to move the applications around, and when you use absolute imports inside the package, if you use the same application later inside a differently-named project, you won't have to rewrite all the imports to reflect the different project name.

Chris B. · Accepted Answer · 2010-01-06 03:32:08Z

How are you packaging your modules normally? If you're packaging them all under the "myproject" module, you should just keep doing that. If you're not, there's no reason to start. I don't see that being in a Django project has anything to do with the question--if you're not reusing code, why bother segregating your packages?

But really, the bigger point is that you're not thinking about how to package and distribute your libraries in a broader sense. Even if they're just a collection of handy utility routines, and you don't intend to share them, you should be thinking about namespace issues. The Python Tutorial has a good basic discussion of the concepts.

Collectives™ on Stack Overflow

What's the suggested way of importing modules within a django project

3 Answers 3

Comments

Comments

Comments

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

Comments

Related