In this talk Marc Tamlyn (@mjtamlyn) was explained to us all the changes in the new “major” version of django, django 1.5.
As always you can find the original talks in Internet: https://speakerdeck.com/mjtamlyn/whats-new-in-django-1-dot-5
futureyou can had this behaviour before (1.3?) but… who use
You can see a better explanation of this points here:
This was a problem since 2014 when Django was created.
If you want to change something this is your first start point:
auth.models.AbstractUser. If you want to go one step forward:
You can override
USERNAME_FIELD too, to override the standard username
field of the model.
contrib.admin integration. Which I didn’t try yet (Álex) but if it
works as they said, it should be just amazing!
Caveats: MySQL, PIL, Selenium… this all need to be migrated also :(
Armin (@mitsuhiko) said that PIL is already supported o/
ALLOWED_HOSTS is a whitelist backported to django 1.3.x and 1.4.x but
required in 1.5.
You can read the django documentation about this here: https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts
Fixes the handling of streaming http responses. Instead use the normal
.content you need to use
streamed_content if you want to access to
update_fieldsis a new variable received on the save method that allows you to know what are the fileds that has changed.
django-admin.py cleanupclear up the sessions, actually, now it’s called
LOGIN_URLcan be an url name now, and django will make the
index_together, create a indexes with several fields.
django.utils.text.slugifyget an string in and returns an slug for you.