As Simon noted in a ticket [1], "Since the introduction of contrib application migrations in 1.8 (#22170 <https://code.djangoproject.com/ticket/22170>) the documented custom user test models <https://docs.djangoproject.com/en/1.9/topics/auth/customizing/#custom-users-and-testing-fixtures> 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 either from a vendored version of Django or a copy-pasta of the documentation suggested usage <https://github.com/search?l=python&q=django+ExtensionUser&ref=searchresults&type=Code&utf8=%E2%9C%93> I think we can safely assume it's not commonly used among third-party application who claim to support custom user models."
Any objection to removing those models from documentation in 1.8 and 1.9 and removing the models themselves in 1.10? (Actually, the models would be moved into the test suite instead of shipped in django/contrib/auth/tests/custom_user.py -- this is done in [2].) [1] https://code.djangoproject.com/ticket/26089 [2] https://github.com/django/django/pull/5975 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7391b65c-71a6-49bd-95bb-908ba3bf120b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
