Multiple profile models via AUTH_PROFILE_MODULES (proposal)

[Alexandru Plugaru]

I was developing a few apps that required some data stored to users profile. Since now there can be only one model that can be used as a profile and the way around it is somewhat ugly, I've made some changes to get_profile method. In settings instead of:

AUTH_PROFILE_MODULE = "app_label.model"

you can do this:

AUTH_PROFILE_MODULES = ("app_label1.model", "app_label2.model", )

[anonymous]

Your patch is not properly generated, so trac does not recognize it.

From the contributing document:

Submit patches in the format returned by the svn diff command. An exception is for code changes that are described more clearly in plain English than in code. Indentation is the most common example; it’s hard to read patches when the only difference in code is that it’s indented.

Patches in git diff format are also acceptable.

[Alexandru Plugaru]

models.py diff SVN format

[Russell Keith-Magee]

My preference would be to deprecate the use of AUTH_PROFILE_MODULES, not enhance it.

The related object manager for OneToOne fields already cache the remote object, so there isn't any caching benefit to had here -- _profile_cache is a historical artefact.

On top of that, you appear to be proposing that we modify get_profile so that it might return multiple objects, depending on the value of a setting.

Marking wontfix. I can't say I'm a fan of this proposal. Feel free to start a discussion on django-dev if you want to advocate for this idea.