#11809: Unable to test a non-db dependent django app without db configuration
------------------------------------------------------------------------+---
Reporter: Prabhu Subramanian <[email protected]> |
Owner: nobody
Status: closed |
Milestone:
Component: Testing framework |
Version: 1.1
Resolution: wontfix |
Keywords:
Stage: Unreviewed |
Has_patch: 0
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------------------------------+---
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
I'm going to mark this wontfix - at least for now.
Like it or not, Django is a framework for building database-backed web
sites. There may well be use cases for various parts of Django without
using a database, but many parts of Django's internals rely on the
notional existence of a database connection.
When the the deprecation of pre-multi-db settings has been completed, this
will be a lot easier to implement - because the single database will
become a list of databases, a list of 0 databases becomes a valid option.
However, for the moment, we need to rely on the existence of a single
database connection.
A workaround that hasn't been mentioned is writing your own test runner;
subclassing the django test runner, and removing/nulling out the create
database checks.
--
Ticket URL: <http://code.djangoproject.com/ticket/11809#comment:4>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
