#7715: admin_tests failures when running Django tests in one natural fashion
---------------------------------------+------------------------------------
Reporter: mtredinnick | Owner: nobody
Status: new | Milestone:
Component: Unit test system | Version: SVN
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Comment (by mtredinnick):
Instead of asking testers to not use the most obvious name in the world
for their settings files, probably better for the tests themselves to ask
for something with an unlikely name, e.g. `qwertyuiopxxy67.py`.
I realise now, too, that the initial report was conflating two different
problems. One is the `settings.py` issue you've discovered. The other is
that when I use `settings3.py`, which I also checked with, I was getting a
different error due to something my PostgreSQL install was spitting out to
stderr that was confusing the tests. So that one was a side issue that
will affect maybe 6 people in the whole world, whereas the SQLite tests
were always failing because of the problem you've found.
--
Ticket URL: <http://code.djangoproject.com/ticket/7715#comment:4>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
