>
> I don't know of a single framework out there besides Django that ships
> with a fixed model for its users.
>
I totally understand this, but I also think the fact that Django *does*
ship with this stuff creates a baseline security and quality for logging
into most Django-powered web apps. I'
I very much share Tai's concerns about the swappable user model introducing
incompatibilities. Imagine two apps, each of which requires an "age"
attribute on the user model. But suppose one of those apps expects age to
be the number of years since that user's birth and one of those apps
expects
The Django admin is a major—if not *the* major—selling point to
budding developers. I worry that externalizing it (hence making it a
*separate* piece of software that needs to be discovered and
installed, which seems simple but can be quite a challenge to new
coders) might take away Django's non-ex
I think this is a great idea! I would certainly benefit from it.
It might be worth considering if there are any methods for passing a
callback function that are better than GET parameters—though I can't
think of any off the top of my head.
H.
On Jun 13, 12:16 am, Alex Kamedov wrote:
> Hi all!
>
