#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+---------------------------------------
Comment (by russellm):
@carljm -- I don't think the "models in test models" thing is documented,
but it's definitely in wide use -- Django's own test suite has a couple of
places where models are defined in the tests package -- (e.g., the
app_cache tests). In most cases it's a non-issue, because if you're
running the tests for a module, then you're probably importing everything
in that module anyway. This is an odd case because the auth tests won't be
run, but the models we want are stored in the auth tests.
Based on your feedback, I'll commit a patch to docs that clarifies the
need for an explicit import.
--
Ticket URL: <https://code.djangoproject.com/ticket/21164#comment:13>
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.3ab7dad6d1c0932218c3d17e3ecbd1d7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
