#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: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Changes (by Simon Greenhill):
* status: new => closed
* needs_better_patch: => 0
* component: Uncategorized => Unit test system
* needs_tests: => 0
* summary: Django uses two different domains as defaults => Django uses
"testserver" instead of "example.com" in
assertRedirects tests
* needs_docs: => 0
* resolution: => invalid
Comment:
I believe it's because django.test.testcases.TestCase.assertRedirects
treats ``testserver`` differently?
--
Ticket URL: <http://code.djangoproject.com/ticket/7743#comment:1>
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
-~----------~----~----~----~------~----~------~--~---
