Opened 13 years ago

Closed 10 years ago

#2373 closed enhancement (wontfix)

Add support for multiple profile modules

Reported by: david@… Owned by: Adrian Holovaty
Component: Contrib apps Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


I would like to change AUTH_PROFILE_MODULE to AUTH_PROFILE_MODULES. This would allow a project that has multiple optional applications to have a per-application profile. The get_profile() in django.contrib.auth would need to be updated to iterate through all of the supplied modules and combine all of the returned profile items as one comprehensive profile. I'm not familiar with the format of what model._default_manager.get( would return, so I'm not sure this would be possible without further modifications there.

Change History (4)

comment:1 Changed 13 years ago by david@…

It seems model._default_manager.get( returns a QuerySet? If this is the case, is it possible to manipulate a QuerySet and add arbitrary fields? Or, can get_profile() be modified to return a collection of them? If the 2nd option is the only way, this change would need to happen before version 1 as it would break compatibility.

comment:2 Changed 13 years ago by david@…

Resolution: wontfix
Status: newclosed

After some discussion on IRC, I've decided to pursue a more generic approach. Once I have something put together, I'll post back with the results.

comment:3 Changed 10 years ago by itsnotvalid

Resolution: wontfix
Status: closedreopened

Just found myself in this situation but apparently there were no fix or I missed something along the way.

comment:4 Changed 10 years ago by James Bennett

Resolution: wontfix
Status: reopenedclosed

Unless you have an actual proposal, including code, the appropriate thing is for this ticket to stay closed. And if you have such a proposal, the appropriate thing is to take it to the dev list for discussion. And since the original description of the ticket involves a change that's backwards-incompatible we can't make that change while maintaining a guarantee of backward compatibility in 1.x Django releases, so at any rate this ticket stays closed.

Note: See TracTickets for help on using tickets.
Back to Top