#19753: Custom user system shouldn't be dependent on all installed apps
-------------------------------+--------------------------------------
Reporter: abraham@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: contrib.auth | Version: 1.5-beta-1
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by russellm):
@anon - the problem isn't "Any third party module that is dependent on a
custom User". You can write a module that has foreign keys to the custom
User, for example. What you can't do is have module level initialization
logic that depends on the pluggable user. The docs already reference one
specific case where this is an issue -- signals -- but if there are other
common use cases for this, then perhaps they need to be documented. As
@charettes and @aaugustin have pointed out, this is a fundamental problem
with the load sequence for Django apps, which should be addressed by
#3591.
So - What's the use case (beyond signals) that requires a module-level
reference to the swappable User model?
--
Ticket URL: <https://code.djangoproject.com/ticket/19753#comment:6>
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.
For more options, visit https://groups.google.com/groups/opt_out.
