Django - non app specific models.py?

Question

I have multiple Django apps, and I have some code in one of my models.py that really applies to all of the apps. Is there a way to move it somewhere generic, outside of a specific app folder?

Examples of non app specific code I have:

def update_groups(sender, user=None, ldap_user=None, **kwargs):
    ...

django_auth_ldap.backend.populate_user.connect(update_groups)

A function to correctly identify users, and connect to the correct signal.

I also have a model proxy of django.contrib.admin.models.LogEntry and a modelAdmin of that model proxy so users in the admin site can view the change history. But these really don't belong in any one app's models.py.

Silver Light · Accepted Answer · 2011-04-04 13:05:32Z

2

Well, just create a python module somewhere in your project and then refference it in your models. To do this, you need a directory with __init__.py file:

helpers/
   __init__.py 
   functions.py

Put your code into the functions.py and in any other place you will be able to:

from helpers.functions import update_groups
post_save.connect(update_groups)

Name of the module is up to you, ofcourse.

answered Apr 4, 2011 at 13:05

Silver Light

46.3k36 gold badges126 silver badges165 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

tiagoboldt Over a year ago

This is a better approach that the one I've suggested if you don't have any models that you want to extend in it. If you do, do create a template app and use class hierarchy

Greg Over a year ago

That's a start, but then one model in one app will be calling "post_save.connect(update_groups)" and it will be kind of arbitrary which app does that. I was hoping there was a concept of a site-wide models.py or some other module that gets imported early.

Silver Light Over a year ago

@Greg, I think that custom modules are best way to share a code in this case. As for the signals, you need to specify the sender, ofcourse, then django will know which model has sent it.

Greg Over a year ago

That <would work> but the code isn't specific to any one app, so why should any one app import helper and call the signal? It seems like there should be a way to preload site-wide stuff.

tiagoboldt · Accepted Answer · 2011-04-04 13:06:17Z

2

You could create a template app that could be used or extended (class hierarchy) by all your other apps that could use that code.

answered Apr 4, 2011 at 13:06

tiagoboldt

2,4161 gold badge24 silver badges30 bronze badges

2 Comments

Silver Light Over a year ago

This is an interesting info. Can you provide a link on creating template apps?

tiagoboldt Over a year ago

that's more software design knowledge than django itself, still, refer to the following: docs.djangoproject.com/en/dev/topics/db/models/… ||| docs.python.org/tutorial/classes.html#inheritance ||| diveintopython.org/object_oriented_framework/… || Good luck

Greg · Accepted Answer · 2011-04-04 14:12:30Z

1

__init__.py in my project's directory seems to be a good place to put this stuff. It gets run right away when the server starts so it's available to everything else. It seems to work fine so far.

answered Apr 4, 2011 at 14:12

Greg

47.5k91 gold badges239 silver badges298 bronze badges

Collectives™ on Stack Overflow

Django - non app specific models.py?

3 Answers 3

4 Comments

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

4 Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related