#11809: Unable to test a non-db dependent django app without db configuration
------------------------------------------------------------------------+---
Reporter: Prabhu Subramanian <[email protected]> |
Owner: nobody
Status: new |
Milestone:
Component: Testing framework |
Version: 1.1
Resolution: |
Keywords:
Stage: Unreviewed |
Has_patch: 0
Needs_docs: 0 |
Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------------------------------+---
Changes (by kmtracey):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Note you have said what you don't like without proposing what you would
like instead. Some special setting to tell the test runner no database is
needed? The test runner to figure out for itself if a database is needed?
I don't see how the former is any better than just setting DATABASE_ENGINE
to sqlite3. The latter strikes me as more trouble than it is worth for
the small fraction (I'm guessing) of users who are running no-database
Django apps. But I haven't given it a great deal of thought, particularly
since you haven't actually said what it is you are proposing so perhaps
you have something completely different in mind.
--
Ticket URL: <http://code.djangoproject.com/ticket/11809#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
