Re: deprecation of AUTH_PROFILE_MODULE

2013-03-03 Thread Daniel Greenfeld
I agree that email-as-username should be a built-in User abstract model (or something) in Django. It's an incredibly common use case and for once I think Django could use some additional functionality. +1 to email as username model in core. Danny On Sunday, March 3, 2013 10:21:55 AM UTC-8,

Re: deprecation of AUTH_PROFILE_MODULE

2013-03-03 Thread Florian Apolloner
Hi Jacob, On Sunday, March 3, 2013 5:08:24 PM UTC+1, Jacob Kaplan-Moss wrote: > > I actually strongly disagree: I think Django *should* ship an > "authenticate-using-email" system. > Out of curiosity, since I barely have this need by myself: Is it "authenticate-using-email" or

Re: deprecation of AUTH_PROFILE_MODULE

2013-03-03 Thread Jacob Kaplan-Moss
On Fri, Mar 1, 2013 at 12:04 PM, Florian Apolloner wrote: > Doing it outside of Django core if fine, inside core is -0 to -1 from me. I actually strongly disagree: I think Django *should* ship an "authenticate-using-email" system. It's *SUCH* a common desire, and it's

Re: deprecation of AUTH_PROFILE_MODULE

2013-03-01 Thread Florian Apolloner
Hi, On Friday, March 1, 2013 9:00:28 PM UTC+1, Luke Sneeringer wrote: > > I'd be interested in actually doing this if folks on the list think it's a > good idea. > Doing it outside of Django core if fine, inside core is -0 to -1 from me. Cheers, Florian -- You received this message because

Re: deprecation of AUTH_PROFILE_MODULE

2013-03-01 Thread Luke Sneeringer
I do think that there's a pretty common "alternate use case" which we could support more easily. That's the use case where someone wants a User model that is either: * exactly like the Django User model, but with e-mail address as the unique identifying field instead of username * exactly

Re: deprecation of AUTH_PROFILE_MODULE

2013-02-27 Thread Russell Keith-Magee
On Thu, Feb 28, 2013 at 4:24 AM, Alper Çuğun wrote: > > I looked into this today with 1.5 hitting and working on a project and > this seemed relevant. > > On Monday, 2 May 2011 19:22:53 UTC+2, Carl Meyer wrote: > >> 1. A specification of the minimal useful interface for a User

Re: deprecation of AUTH_PROFILE_MODULE

2013-02-27 Thread Alper Çuğun
I looked into this today with 1.5 hitting and working on a project and this seemed relevant. On Monday, 2 May 2011 19:22:53 UTC+2, Carl Meyer wrote: > 1. A specification of the minimal useful interface for a User (perhaps > > in the form of an abstract base model?) > A User should not require

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Russell Keith-Magee
On Mon, May 2, 2011 at 10:54 PM, Carl Meyer wrote: > On 05/02/2011 07:15 AM, Russell Keith-Magee wrote: what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() or removing the suggestion to use it from the docs in 1.4 release? There are broader

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Russell Keith-Magee
On Tue, May 3, 2011 at 1:28 AM, Shawn Milochik wrote: > Since it wasn't stated explicitly in that last wish-list, I'd like to add: > No assumption that the primary key is an integer. Certainly worth stating, but I don't think it's a major technical challenge. An abstract base

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Jannis Leidel
On 02.05.2011, at 19:22, Carl Meyer wrote: > On 05/02/2011 11:38 AM, Jeremy Dunck wrote: >> Given a blank slate, what would Auth look like these days? And can we >> work towards that? > > Now, why you gotta get all constructive and forward-thinking and stuff? ;-) > > Here's my list of core

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Shawn Milochik
Since it wasn't stated explicitly in that last wish-list, I'd like to add: No assumption that the primary key is an integer. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Carl Meyer
On 05/02/2011 11:38 AM, Jeremy Dunck wrote: > Given a blank slate, what would Auth look like these days? And can we > work towards that? Now, why you gotta get all constructive and forward-thinking and stuff? ;-) Here's my list of core ideal-contrib.auth desiderata that I keep seeing crop up in

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Jeremy Dunck
On Mon, May 2, 2011 at 9:54 AM, Carl Meyer wrote: ... > I don't mind leaving get_profile() around, I guess, but IMO the best > argument that can be made for that is "it's useless but mostly harmless, > and it's not worth making people change their code to remove it." I'll >

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Carl Meyer
On 05/02/2011 07:15 AM, Russell Keith-Magee wrote: >>> what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() >>> or removing the suggestion to use it from the docs in 1.4 release? >>> There are broader issues with extending User model but I think this one >>> can be handled

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-02 Thread Russell Keith-Magee
On Mon, May 2, 2011 at 1:40 AM, Karen Tracey wrote: > On Sun, May 1, 2011 at 12:39 PM, Mikhail Korobov > wrote: >> >> Hi folks, >> what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() >> or removing the suggestion to use it from

Re: deprecation of AUTH_PROFILE_MODULE

2011-05-01 Thread Karen Tracey
On Sun, May 1, 2011 at 12:39 PM, Mikhail Korobov wrote: > Hi folks, > > what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() > or removing the suggestion to use it from the docs in 1.4 release? > There are broader issues with extending User model but

deprecation of AUTH_PROFILE_MODULE

2011-05-01 Thread Mikhail Korobov
Hi folks, what do you think about deprecating AUTH_PROFILE_MODULE and .get_profile() or removing the suggestion to use it from the docs in 1.4 release? There are broader issues with extending User model but I think this one can be handled separately. Some links: *