Tentative multi-db testing strategy
Merge branch 'develop' into yakky-feature/multidb_test

Conflicts:
	cms/test_utils/cli.py
	runtests.py
multi db testing
actually use the db env
fixed a lot of tests for mysql
slqite fixed, mysql fixed (except too many queries)
all tests passing on: sqlite, mysql, postgres
django 1.3 and postgres fixes
missed a file
cleanup
cleanup2
using localhost for postgres
Merge branch 'develop' into multidb_test

Conflicts:
	cms/signals.py
	cms/tests/page.py
fixed signals
Smarter way of handling settings

Removed monkeypatching from cms.__init__
Removed cms.conf.*
Added cms.utils.conf.get_setting(name)
Refactored all (CMS) setting accesses throughout the code base

This should fix issues with more recent gunicorn version (>0.12) as
well as make the code less hacky.

Known issues on this branch:

* ApphooksPageLanguageUrlTestCase.test_page_language_url_for_apphook
  currently fails, not sure why.
* SettingsTests.test_cms_templates_length,
  SettingsTests.test_cms_templates_none and
  SettingsTests.test_cms_templates_valid all fail currently because
  cms.conf.patch.post_patch and cms.conf.patch.post_patch_check are
  no longer available.
Merge branch 'develop' into multidb_test

Conflicts:
	cms/tests/page.py
new database url scheme
fixed some postgres errors
python2.5 compat
cleanup