The two big headline features, the configurable User model and Python 3 support, are both huge. The first, because as is right now, simply extending the User model feels janky and possibly broken, and the second, because Django is probably one of the biggest reasons people have not moved onto Python 3.
> Configurable User model<p>This pleases me greatly. No longer do I need to rely on plug-ins (and therefore, them being updated) to minimally extend the existing User model for small projects.
Major Highlights:<p>- Python3 support! (supports python2.6.5+ and python3.2+ in the same code base)<p>- {% verbatim %} (no collision problems with mustache)<p>- Built-in Partial model saving
If I want to create my own database and write my own SQL queries instead of using Django's object models and ORM, does it still make sense to use Django's user model in my project?
Can someone point me to a compare/contrast sort of doc between modern Django and Rails? I don't do a lot of web app programming, but I'm curious as to whether there's much of a difference between the two.