#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):
Yeah, you're right about not being able to change it. I'm not too worried
about the hard-coded behaviour of manage.py, since it's just a tool for
getting started, but not breaking it would be cool. And it's pretty much a
given that having something importable named after the settings file
you're trying to use will fail. That's just the way Python works.
Kind of annoying to not be able to use settings.py for the test settings
(I now have two years or so of muscular memory to unlearn when running
tests), but maybe it's unavoidable if we want to test this stuff. C'est la
vie. :-(
--
Ticket URL: <http://code.djangoproject.com/ticket/7715#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
