#9717: manage.py flush raises error if there are unsynchronized applications
--------------------------------------+-------------------------------------
Reporter: russellm | Owner: nobody
Status: new | Milestone:
Component: django-admin.py | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by russellm):
Replying to [comment:2 julien]:
> So, I guess that to properly test this, one would need to be able to
include apps dynamically in the test suite, a problem which #7835 is
trying to solve. Looks like a "chicken or the egg" puzzle :)
This is one of the rare occasions where it is acceptable to not include a
unit test with a patch. There are a number of areas of Django that aren't
unit tested - for example, most of the behaviour of syncdb is not formally
tested. This isn't ideal, but sometimes it is unavoidable - usually
because the cost of setting up the infrastructure required for testing
these edge cases vastly exceeds the benefit that will be returned,
especially given the frequency with which those areas of code are modified
is taken in to consideration.
I'll take a look at this patch tonight.
--
Ticket URL: <http://code.djangoproject.com/ticket/9717#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
-~----------~----~----~----~------~----~------~--~---
