http://simonwillison.net/2009-05-12T13:19:25+00:00Simon Willison2009-05-12T13:19:25+00:002009-05-12T13:19:25+00:00https://simonwillison.net/2009/May/12/contextual/#atom-tag

<p><strong><a href="http://pypi.python.org/pypi/Contextual">Contextual</a></strong></p> I’ve been trying to figure out a sane way to replace Django’s settings.py global module with something that’s designed to be reconfigured at run-time. Contextual appears to be trying to solve exactly that problem. <p><small></small>Via <a href="http://groups.google.com/group/paste-users/browse_thread/thread/7346e75940413f46">A discussion on Paste Users</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/contextual">contextual</a>, <a href="https://simonwillison.net/tags/django">django</a>, <a href="https://simonwillison.net/tags/globals">globals</a>, <a href="https://simonwillison.net/tags/python">python</a>, <a href="https://simonwillison.net/tags/settings">settings</a></p>

2009-02-12T12:30:00+00:002009-02-12T12:30:00+00:00https://simonwillison.net/2009/Feb/12/relocatable/#atom-tag

<p><strong><a href="http://morethanseven.net/2009/02/11/django-settings-tip-setting-relative-paths/">Django Settings Tip - Setting Relative Paths</a></strong></p> This is the first thing I do in every single one of my Django projects—it makes projects relocatable to other machines with just a couple of lines of code. I wouldn’t be at all upset to see it added to the default Django settings.py file created by ./manage.py startproject <p>Tags: <a href="https://simonwillison.net/tags/django">django</a>, <a href="https://simonwillison.net/tags/gareth-rushgrove">gareth-rushgrove</a>, <a href="https://simonwillison.net/tags/python">python</a>, <a href="https://simonwillison.net/tags/settings">settings</a></p>

2007-12-21T10:45:53+00:002007-12-21T10:45:53+00:00https://simonwillison.net/2007/Dec/21/empty/#atom-tag

<p><strong><a href="http://blog.michaeltrier.com/2007/12/21/using-unipath-to-keep-thing-portable">Using Unipath to Keep Things Portable</a></strong></p> Django tip to avoid hard-coding full paths. I usually set a global called OUR_ROOT in settings.py using os.path.dirname(__file__) and use os.path.join with it to construct any other paths that I need. <p>Tags: <a href="https://simonwillison.net/tags/django">django</a>, <a href="https://simonwillison.net/tags/michael-trier">michael-trier</a>, <a href="https://simonwillison.net/tags/python">python</a>, <a href="https://simonwillison.net/tags/settings">settings</a>, <a href="https://simonwillison.net/tags/unipath">unipath</a></p>

2007-11-27T15:01:50+00:002007-11-27T15:01:50+00:00https://simonwillison.net/2007/Nov/27/max/#atom-tag

<p><strong><a href="http://maxischenko.in.ua/blog/entries/130/using-djangonewforms-with-pylons/">Using django.newforms with Pylons</a></strong></p> It’s always good to see Django components used outside of the framework itself. For the record, you can avoid the DJANGO_SETTINGS_MODULE environment variable entirely using django.conf.settings.configure (search for it). <p>Tags: <a href="https://simonwillison.net/tags/django">django</a>, <a href="https://simonwillison.net/tags/newforms">newforms</a>, <a href="https://simonwillison.net/tags/pylons">pylons</a>, <a href="https://simonwillison.net/tags/python">python</a>, <a href="https://simonwillison.net/tags/settings">settings</a></p>