Skip to main content

Ways Django Can Import Things

How many ways can django import a module?

Grep is hard for this.

In .py files

"import (.*)\..*"
"from (.*)\..* import .*"
"patterns\(['"](.*)['"]"
"url(r?['"].*, ['"](.*)"


In INSTALLED_APPS and other settings.

Am I missing any? Better question: Why do I have to wonder if I'm missing any?

Comments

Doug Napoleone said…
You forgot about the magic __path__ hack done to the templatetags 'package' directory. It turns out that app.templatetags.app and django.templtatetags.app are two DIFFERENT imports of the same code and are independent modules with their own globals and locals...

Think about that for a while...
James Bennett said…
You did actually miss one: django.utils.importlib, which is simply a copy of the available-in-future-Python importlib module that Brett Cannon helpfully backported for us to handle all the things in Django (think pluggable backend modules) which require dynamic imports. Previously we used Python's raw __import__ for that, and importlib makes it ever so much simpler, and generally they have to in order to support the sort of dynamic-but-still-concise stuff people like to do in Python.

Anyway, two of the things you've listed are just standard Python import statements, and the other two are just URL-pattern functions which -- if it bugs you that much -- will happily accept the actual callable (or an iterable of patterns, in the case of include()) instead of strings. The string option is mostly just a convenience.

So I'm not sure I really understand the "why do I have to wonder if I'm missing any"; lots of frameworks/libraries have ways to specify something as a string and get it dynamically imported later through some mechanism other than a direct "import whatever" statement.

Oh, and for Doug: the __path__ hacking for templatetags is finally gone in trunk, which means it won't be in 1.2. The last bit of "magic" from magic-removal is finally out, hallelujah.
Not sure if it is what you were intent on capturing, but there is the import of the Django settings file as a special sort of case. I recently posted some stuff about that at http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html.
James said…
__import__( ... )
Robert said…
Wouldn't it be nice to standardize these 'import later module strings'* that various python frameworks have as some sort of generic-ized deferredimport('some.python.path.etc') object?

*: which are sometimes necessary due to definition order and cyclic dependencies etc.

Popular posts from this blog

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …