#21164: get_user_model() does not handle custom user models for testing purposes
-----------------------------------+---------------------------------------
Reporter: raymond.penners@… | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 1.6-alpha-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+---------------------------------------
Changes (by russellm):
* version: 1.5 => 1.6-alpha-1
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Ok - now I see what's going on - this is a regression that has been
introduced in 1.6 as a result of the introduction of the new discovery
test runner. Your sample project runs fine under Django 1.5.
In Django 1.5, the auth tests are loaded, which causes the test users to
be loaded as well. In Django 1.6, the discovery test runner means that the
auth tests aren't executed - and as a result, the test Users aren't
installed.
I'm not sure what the fix will be here, but it's clearly a change in
behavior that needs to be dealt with before the final release.
Thanks for being politely persistent :-)
--
Ticket URL: <https://code.djangoproject.com/ticket/21164#comment:8>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/084.8ade2a0bb7cbd7992f2d8ee1d4a21a97%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
