Re: [Django] #2373: Add support for multiple profile modules

[Django]

#2373: Add support for multiple profile modules
-+--
  Reporter:  da...@dawninglight.net  | Owner:  adrian
Status:  closed  | Milestone:
 Component:  Contrib apps|   Version:
Resolution:  wontfix |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

  * status:  reopened => closed
  * resolution:  => wontfix

Comment:

 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.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2373: Add support for multiple profile modules

[Django]

#2373: Add support for multiple profile modules
-+--
  Reporter:  da...@dawninglight.net  | Owner:  adrian
Status:  reopened| Milestone:
 Component:  Contrib apps|   Version:
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by itsnotvalid):

  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2373: Add support for multiple profile modules

[Django]

#2373: Add support for multiple profile modules
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian 
 Type:  enhancement |   Status:  closed 
 Priority:  normal  |Milestone: 
Component:  Contrib apps|  Version: 
 Severity:  normal  |   Resolution:  wontfix
 Keywords:  |  
+---
Changes (by [EMAIL PROTECTED]):

  * resolution:  => wontfix
  * status:  new => closed

Comment:

 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.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #2373: Add support for multiple profile modules

[Django]

#2373: Add support for multiple profile modules
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement |   Status:  new   
 Priority:  normal  |Milestone:
Component:  Contrib apps|  Version:
 Severity:  normal  |   Resolution:
 Keywords:  |  
+---
Comment (by [EMAIL PROTECTED]):

 It seems model._default_manager.get(useridexact=self.id) 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.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

[Django] #2373: Add support for multiple profile modules

[Django]

#2373: Add support for multiple profile modules
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  enhancement |  Status:  new   
 Priority:  normal  |   Milestone:
Component:  Contrib apps| Version:
 Severity:  normal  |Keywords:
+---
 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(user__id__exact=self.id) would return, so I'm
 not sure this would be possible without further modifications there.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---