… admin's delete confirmation page.
…urn an iterator.
…compatibility. Thanks Tom Christie for the report and review.
…ated() use Using select_related() after .values() or .values_list() is not possible because .values() or .values_list() already got the values they need.
…G is False Thanks to Keryn Knight, Curtis Maloney and Tim Graham for their reviews.
With this change, it's expected to survive anything except errors that make it impossible to import the settings. It's too complex to fallback to a sensible behavior with a broken settings module. Harcoding things about runserver in ManagementUtility.execute is atrocious but it's the only way out of the chicken'n'egg problem: the current implementation of the autoreloader primarily watches imported Python modules -- and then a few other things that were bolted on top of this design -- but we want it to kick in even if the project contains import-time errors and django.setup() fails. At some point we should throw away this code and replace it by an off-the-shelf autoreloader that watches the working directory and re-runs `django-admin runserver` whenever something changes.
Changed the way makemessages invokes xgettext from one call per translatable file to one call per locale directory (using --files-from). This allows to avoid https://savannah.gnu.org/bugs/index.php?35027 and, as a positive side effect, speeds up localization build.
Previously, messages of ERROR level or higher were printed to the console.
This speeds up import of 'django.core.validators' which can save a few hundred milliseconds when importing the module for the first time. It can be a significant speedup to the django-admin command.
…lashes with a model reverse accessor.
Fixed a regression introduced in e1427cc when running tests in reverse order.