Databases
StackOverflow2013
Postsdbo
PODjango application override & import path?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODjango application override & import path?
    primarykey
    data
    text
    <p>Let's have a django project using a 3rd party application. I'd like to override some of its modules without touching original files. Simple subclassing is not possible here, need to override code transparently as many other apps rely on original class names and functions.</p> <p>Project's structure looks like:</p> <pre><code>django_project/ __init__.py settings.py overrides/ &lt;-- here is a subdir with apps overrides __init__.py payment/ &lt;-- here is an example of app to override __init__.py admin.py forms.py &lt;-- this file is ignored, original is imported models.py tests.py views.py </code></pre> <p><code>settings.py</code> was modified with</p> <pre><code>INSTALLED_APPS=( 'satchmo_store.shop' #'payment' # original values 'overrides.payment' # modified app ... ) </code></pre> <p>The above solution however does not work, because Django does not insert path of added app into modules search path (<code>sys.path</code>). Django just loads <code>admin.py</code>, <code>models.py</code>, <code>tests.py</code> and <code>views.py</code>, other files like <code>forms.py</code> are ignored.</p> <p><strong>Is this behaviour documented somewhere ? What exactly placing a module name in INSTALLED_APPS does behind scenes ?</strong></p> <p>I hacked the situation with hardcoding new modules search path in <code>manage.py</code> and Apache's setting of WSGIPythonPath.</p> <pre><code>import os.path import sys DIRNAME = os.path.dirname(__file__) APPS_OVERRIDE = os.path.join(DIRNAME, 'overrides') if not APPS_OVERRIDE in sys.path: sys.path.insert(1, APPS_OVERRIDE) </code></pre> <p>I doubt this is the right way. Cann't find a guide describing apps overriding.</p> <p><strong>So, how can I properly override external Django application in my project ?</strong></p> <p>The bonus question: <strong>Do I need to copy whole application directory tree, not just particular files which are really modified ?</strong> As far as I know, Python stops at first matching module path, so it won't import other modules available in following parts of the search path.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDavid Unric
    1. USDavid Unric
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODjango application override & import path?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODjango application override & import path?
      1. USDavid Unric
      1. VTBountyStart
    3. VO
      singulars
      1. PODjango application override & import path?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COProperly overriding... fork the project unless there is a hook in the project somewhere. The easy fix (which isn't always possible), monkeypatching by changing the code after import. As far as I know there is no documentation about the behaviour but the rule of thumb for me is always, if you want to override smoething, do it in the `models.py` since that always gets imported as the first part.
      singulars
      1. PODjango application override & import path?
      1. USWolph
    2. CO@Wolph So how do I have to apply `overrides.payment.form` to transparently replace the original `payment.form` ? Monkey patch whole module in `overrides.payment.module` ?
      singulars
      1. PODjango application override & import path?
      1. USDavid Unric
    3. COI've added an example as an answer, try and play around with that :)
      singulars
      1. PODjango application override & import path?
      1. USWolph
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload