On Tuesday, September 18, 2012 9:34:38 PM UTC-4, dstufft wrote:
>
> On Tuesday, September 18, 2012 at 9:13 PM, Ben Slavin wrote:
>
> Lastly, I haven't seen a path to easily allow third-party apps to 
> gracefully support both The Old Way and The New Way (1.4 and 1.5). It feels 
> a bit wrong, but should we be considering  the addition of get_user_model 
> and settings.AUTH_USER_MODEL to 1.4.x that's hardcoded to contrib.auth.User 
> so third-party apps can rely on the presence of these mechanisms?
>
>  I don't think adding a hardcoded AUTH_USER_MODEL is going to give the 
> kind of coverage people would want. Likely the best way would be for people 
> to write a wrapper function around the relevant methods/settings and 
> include it in their own projects. This sucks for duplication across all 
> those projects but otherwise it means they'll only be able to support the 
> latest 1.4.x and 1.5+. Likely to be a better user compatibility story by 
> handling the fallback on a per app basis (Django could provide examples 
> though).
>

I agree that this does limit things to only 1.4.X and 1.5+, but that seems 
acceptable. I did consider the possibility of not adding this support 
layer, but after consideration still felt it will justify the effort.

Those apps that require (or choose to offer) a deeper stack of version 
support can choose to do so, but the pragmatism of making the common case 
easy (and removing the need for cross-project duplication) seems to justify 
the unified interface.

Not speaking as a matter of official policy, but running the latest micro 
version of the previous minor version seems a reasonable requirement for 
third-party app developers to impose.

 - Ben

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/dxid-t-e9LUJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to