Home/ Questions/Q 908543
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T16:44:01+00:00

I’m aware I can store it anywhere in my python path and all, but

  • 0

I’m aware I can “store it anywhere in my python path” and all, but what’s an organized pattern I can use to store middleware classes for my project?

I am appending my project root directory and project directory to the sys path through mod_wsgi:

sys.path.append( '/srv/' )
sys.path.append( '/srv/workarounds/' )

The latter line being the project root. As an example, let’s say I want to apply this middleware class: http://djangosnippets.org/snippets/1179/

Would I just copy the snippet contents into a middleware.py file and dump it in my project root? Create a directory for middleware, add that directory to my python path?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    My usual layout for a django site is:

    projects/
templates/
common/
local/

    Where:

    • projects contains your main project and any others
    • common contains things you may share across sites, or are at least not project-specific, like if you need to download django-profile and django-registration rather than having it directly in python/site-packages
    • templates contains just that
    • local contains things that are going to be specific to the current machine, so that you can have properly separated data, like database location and password – I then soft-link the machine-specific versions (say “machine1-localconfig.py”) to local/localconfig.py and then can “import localconfig” in settings.py

    I generally put middleware that’s project-specific inside a project, and middleware that’s not project-specific in common/middleware/

    Make sure to add the templates directory to the right place in settings (or most probably, localconfig.py and then import it in settings), and makse sure to add the projects, common, and local directories to your PYTHONPATH.

    • 0