2013-03-28 20:02:35 +00:00
|
|
|
==========================
|
|
|
|
|
Django 1.5.1 release notes
|
|
|
|
|
==========================
|
|
|
|
|
|
|
|
|
|
*March 28, 2013*
|
|
|
|
|
|
|
|
|
|
This is Django 1.5.1, a bugfix release for Django 1.5. It's completely backwards
|
|
|
|
|
compatible with Django 1.5, but includes a handful of fixes.
|
|
|
|
|
|
|
|
|
|
The biggest fix is for a memory leak introduced in Django 1.5. Under certain
|
|
|
|
|
circumstances, repeated iteration over querysets could leak memory - sometimes
|
|
|
|
|
quite a bit of it. If you'd like more information, the details are in
|
|
|
|
|
`our ticket tracker`__ (and in `a related issue`__ in Python itself).
|
|
|
|
|
|
|
|
|
|
__ https://code.djangoproject.com/ticket/19895
|
2014-12-19 15:25:57 +00:00
|
|
|
__ https://bugs.python.org/issue17468
|
2013-03-28 20:02:35 +00:00
|
|
|
|
|
|
|
|
If you've noticed memory problems under Django 1.5, upgrading to 1.5.1 should
|
|
|
|
|
fix those issues.
|
|
|
|
|
|
|
|
|
|
Django 1.5.1 also includes a couple smaller fixes:
|
|
|
|
|
|
|
|
|
|
* Module-level warnings emitted during tests are no longer silently hidden
|
2014-12-19 14:54:29 +00:00
|
|
|
(:ticket:`18985`).
|
|
|
|
|
* Prevented filtering on password hashes in the user admin (:ticket:`20078`).
|
