#7743: Django uses "testserver" instead of "example.com" in assertRedirects
tests
---------------------------------------+------------------------------------
Reporter: jshaffer | Owner: nobody
Status: closed | Milestone:
Component: Unit test system | Version: SVN
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by mtredinnick):
* status: reopened => closed
* resolution: => wontfix
Comment:
Was marked as "invalid" a while back, so I assume the reopening was just
the normal "oops, I auto-closed the wrong ticket". This is really
"wontfix", though, since (a) the test framework does treat testserver
specially and (b) introducing any accidental confusion with the use of
example.com in the user's code is worth avioding. It's very clear when you
see `"testserver"` that it's something generated by the test framework.
Finally, (c) the default value of the sites setting is pretty irrelevant
here, since if you are using the sites framework, you will have changed
the value anyway.
--
Ticket URL: <http://code.djangoproject.com/ticket/7743#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
-~----------~----~----~----~------~----~------~--~---
