#11942: testing from a checkout is overly complicated
----------------------------------------+-----------------------------------
Reporter: termie | Owner: nobody
Status: reopened | Milestone:
Component: Testing framework | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------+-----------------------------------
Changes (by termie):
* status: closed => reopened
* resolution: duplicate =>
Comment:
reopening, this is not only about settings.py and databases, it is also:
the django being tested against incorrectly defaults to whatever django is
first on your path rather than the checkout, the tests in the checkout are
obviously written for the code in the checkout and are very unlikely to
work with your installed version of django
additionally, these is no need for the extra --settings command-flag, the
default of looking at settings.py in current directory is perfectly
adequate and should you want to test with different settings using the
settings flag is easy enough, adding a message like "testing with
settings.py, to change this use --settings" would leave the feature with
good discoverability.
regarding assumed defaults there is quite obviously such a thing even if
in this instance it might be preferable to make the choice of databases a
more conscious one, I am happy to leave that argument for the other issue.
--
Ticket URL: <http://code.djangoproject.com/ticket/11942#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
