[Chicago] Django 1.5 AUTH_USER_MODEL
emperorcezar at gmail.com
Thu Nov 29 15:45:40 CET 2012
It's well worth the hassles to get a real custom user model working in my opinion. There's not many options for the Django team in this regard. Either they make the change and deal with the incompatibilities that come with it's _optional_ use, or keep the same old broken system.
If Django kept the same broken system as policy, it would fade away in a few years.
On Nov 29, 2012, at 7:24 AM, Martin Maney <maney at two14.net> wrote:
> I've been chatting with a couple folks who are trying to come to grips
> with some of Django 1.5's new features, and between those discussions
> and reading the docs I'm wondering if this is going to be a big mess.
> Once simple little thing - this is going to break 3rd party apps (if
> you use a custom user model) that haven't been modified to use
> settings.AUTH_USER_MODEL instead of the traditional direct reference
> that wires in the model from contrib, yes? Which would be the vast
> majority of them at this point, I'd expect. ;-(
> It all just seems rather slipshod to me... but then I have been saying
> for quite a while that contrib delanda est.
> We reject kings, presidents, and voting.
> We believe in rough consensus
> and running code. -- David Clarke
> Chicago mailing list
> Chicago at python.org
More information about the Chicago