Thanks Marek Brzóska for the report.

Wrap the Parser.compile_filter method call with a try/except and call the
newly added Parser.compile_filter_error(). Overwrite this method in the
DebugParser to throw the correct error.

Since this error was otherwise catched by the compile_function try/except
block the debugger highlighted the wrong line.

Refs #8404.

Thanks sneawo for the report and Jonathan Loy for the patch.

Thanks coolRR for the report.

This fixes two tests in admin_views which were failing on Python 3, but only if
the tests were run with docutils installed.

The reason was that the except clause needed to remove a connection
from the django.db.connections dict, but other parts of Django do not
expect this to happen. In addition the except clause was silently
swallowing the exception messages.

Refs #19707, special thanks to Carl Meyer for pointing out that this
approach should be taken.

Fixed #19808 -- Typo in example

Thanks Anssi and Marc Tamlyn for reviewing.

Fixes #19803.

This is required by the tzinfo API, see Python's docs.

Also made _get_timezone_name deterministic.

value_annotation isn't very well defined. Before this change, setting it
to datetime.datetime could silently reverse the behavior of isnull
lookups. This commit doesn't have any consequences on the current code.
It's just a safeguard for future ORM hackers.

Thanks to nxvl and slurms for the initial patch, ptone for the review
and timo for the documentation tweaks.

Thanks JonLoy for the patch.

Refs #15295.

Previously it was possible to call clear_ordering without the
force_empty argument. The result was that the query was still ordered
by model's meta ordering if that was defined. By making the arg
mandatory it will be easier to spot possible errors caused by assuming
clear_ordering will remove all ordering.

Thanks to Dylan Klomparens for the suggestion. Refs #19720.

Thanks JonLoy for the draft patch.

When a query had a complex where condition (a condition targeting more
than the base table) a subquery was used for deletion. However, the
query had default ordering from the model's meta and Oracle doesn't
work with ordered subqueries.

The regression was caused by fast-path deletion code introduced in
1cd6e04c for fixing #18676.

Thanks to Dylan Klomparens for the report.

PostgreSQL and Oracle always support transactions, so the create table
and rollback test is non-necessary on those DBs.

Thanks to shai for report.

2b5f8482 based its changes on #19061
that made the is_active attribute mandatory for user models.
The try/except was not removed for the groups_for_user function.

refs #19780

Also bumped django_next_version back to 1.6 so those
annotations are described as "the development version"
in the docs.

Thanks Aymeric for the patch.

Thanks xian at mintchaos.com for the report.

Thanks c.pollock at bangor.ac.uk for the report.

Cleaned up some lingering signals in the test suite that were causing spurious failures with Pypy and Postgres.

Thanks Aymeric Augustin for the report and directions for the patch.

Thanks to Aymeric and Carl for the review.

Also, according to the comments on the ticket and its duplicates, added
tests execising saving an instance of a model with a GFK to:

* An unsaved object -- This actually doesn't generate the same failure
  but another ORM-level exception. The test verifies it's the case.

* An instance of a model with a __nonzero__() method thant returns False
  for it. This doesn't fail because that code path isn't executed.

* An instance of a model with a CharField PK and an empty value for it.
  This doesn't fail.

Thanks Daniele Procida.