#26089: The auth custom test model tables are not created anymore.
-------------------------------------------+---------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: new
Component: contrib.auth | Version: 1.8
Severity: Release blocker | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+---------------------------
Since the introduction of contrib application migrations in 1.8 (#22170)
the [https://docs.djangoproject.com/en/1.9/topics/auth/customizing
/#custom-users-and-testing-fixtures documented custom user test models]
table are not created anymore because they are registered to the `'auth'`
labeled application but are not part of its shipped migrations.
Based on the fact this was not reported before and that the only uses of
`ExtensionUser` I can find is
[https://github.com/search?l=python&q=django+ExtensionUser&ref=searchresults&type=Code&utf8=%E2%9C%93
either from a vendored version of Django or a copy-pasta of the
documentation suggested usage] I think we can safely assume it's not
commonly used among third-party application who claim to support custom
user models. I'll make sure to post the mailing list in order to gather
feedback from the community about this point.
Given the models are simply not usable on 1.8 and 1.9 now I'd like to
start the deprecation in 1.8 in order order to be able to completely
remove them on master but if it's not considered safe enough I came up
with a with a workaround that could be backported since there's still no
documented way to ship test only models (#7835).
If these models are relied on by the community I would suggest we start
deprecating them in 1.10 and adjust the documentation to suggest
subclassing the provided abstract models instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/26089>
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/052.5ab29215803bc275e193ab509af150d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
