Thanks to Michael D. Hoyle for the report and Tim Graham for the review.

Thanks Daniel Hahler for the report and Tim Graham for the review.

Thanks kabakov.as@gmail.com for the report, and Aymeric Augustin,
Simon Charette for the reviews.

Make sure PO catalog text fetched from gettext programs via standard
output isn't corrupted by mismatch between assumed (UTF-8) and real
(CP1252) encodings. This can cause mojibake to be written when creating
or updating PO files.

Also fixes #23311.

Thanks to contributor with Trac nick 'danielmenzel' for the report,
excellent research and fix.

All tests now rely on TEMPLATES.

This avoids leaving projects silently vulnerable when this option is set
to a string instead of a one-item tuple containing that string, a very
common misconfiguration.

Previously, when a template was rendered with RequestContext, inclusion
tags were rendered with a plain context, losing additional information
available in the RequestContext.

The (admittedly bizarre) implementation of RequestContext.new() has the
side-effect of not running template context processors, making this
change backwards-compatible.

dictionary and context_instance and superseded by context.

Refactored tests that relied context_instance with more modern idioms.

*args, **kwargs brought more confusion than concision.

Deprecated features aren't tested.

Adjusted its API through a deprecation path according to the DEP.

This aligns the Django Template Engine API with the common template
backend API.

It wasn't documented and it wasn't used anywhere.

It wasn't documented and it wasn't used anywhere, except in a few tests
that don't test it specifically and can be rewritten with get_template.

This commit changes the return type of these two functions. Instead of
returning a django.template.Template they return a backend-specific
Template class that must implement render(self, context).

i18n is left aside for now.

Since this package is going to hold both the implementation of the Django
Template Language and the infrastructure for Multiple Template Engines,
it should be untied from the DTL as much as possible within our
backwards-compatibility policy.

Only public APIs (i.e. APIs mentioned in the documentation) were left.

The shorter name is just as explicit and, well, shorter.