summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2014-12-29Fixed a vesionadded directive.Florian Apolloner
2014-12-29Fixed #23753 -- Oracle failure with CoalesceJosh Smeaton
2014-12-28Explained the structure of django.template.Aymeric Augustin
2014-12-28Raised a warning when using the legacy TEMPLATE_* settings.Aymeric Augustin
All tests now rely on TEMPLATES.
2014-12-28Deprecated TEMPLATE_CONTEXT_PROCESSORS.Aymeric Augustin
2014-12-28Deprecated TEMPLATE_DIRS.Aymeric Augustin
2014-12-28Deprecated TEMPLATE_LOADERS.Aymeric Augustin
2014-12-28Deprecated TEMPLATE_STRING_IF_INVALID.Aymeric Augustin
2014-12-28Deprecated ALLOWED_INCLUDE_ROOTS.Aymeric Augustin
2014-12-28Raised an error when allowed_include_roots is a string.Aymeric Augustin
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.
2014-12-28Deprecated current_app in TemplateResponse and render(_to_response).Aymeric Augustin
2014-12-28Preserved context class in inclusion_tag.Aymeric Augustin
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.
2014-12-28Deprecated some arguments of django.shortcuts.render(_to_response).Aymeric Augustin
dictionary and context_instance and superseded by context. Refactored tests that relied context_instance with more modern idioms.
2014-12-28Simplified implementation of django.shortcuts.render(_to_response).Aymeric Augustin
*args, **kwargs brought more confusion than concision.
2014-12-28Moved context_processors from django.core to django.template.Aymeric Augustin
2014-12-28Added a comment about the last use of Engine.get_default().Aymeric Augustin
2014-12-28Added tests for django.template.loader.Aymeric Augustin
Deprecated features aren't tested.
2014-12-28Supported multiple template engines in render_to_string.Aymeric Augustin
Adjusted its API through a deprecation path according to the DEP.
2014-12-28Removed extraneous arguments in Engine.from_string.Aymeric Augustin
This aligns the Django Template Engine API with the common template backend API.
2014-12-28Removed private API get_template_from_string.Aymeric Augustin
It wasn't documented and it wasn't used anywhere.
2014-12-28Removed private API find_template.Aymeric Augustin
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.
2014-12-28Supported multiple template engines in get_template and select_template.Aymeric Augustin
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).
2014-12-28Looked up the default template engine in the list of all engines.Aymeric Augustin
2014-12-28Isolated template tests from Django settings.Aymeric Augustin
2014-12-28Passed a reference to the current engine when instantiating Template.Aymeric Augustin
2014-12-28Removed some uses of global APIs from django.template.loader.Aymeric Augustin
2014-12-28Added basic tests for template backends.Aymeric Augustin
2014-12-28Added Django template backend.Aymeric Augustin
2014-12-28Added jinja2 template backend.Aymeric Augustin
2014-12-28Added dummy template backend.Aymeric Augustin
2014-12-28Added initial support for loading template engines.Aymeric Augustin
2014-12-28Imported BaseEngine from the DEP.Aymeric Augustin
i18n is left aside for now.
2014-12-28Cleaned up the django.template namespace.Aymeric Augustin
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.
2014-12-28Renamed get_template_from_string to from_string.Aymeric Augustin
The shorter name is just as explicit and, well, shorter.
2014-12-28Simplified handling of a default value.Aymeric Augustin
2014-12-27Fixed #24056 -- Fixed syntax highlighting in topics/testing/tools.txt.Tim Graham
2014-12-27Fixed #24057 -- Fixed typo in docs/howto/custom-lookups.txt.Christopher Grebs
2014-12-27Added release notes for the last two commits.Aymeric Augustin
2014-12-27Fixed #23831 -- Supported strings escaped by third-party libs in Django.Aymeric Augustin
Refs #7261 -- Made strings escaped by Django usable in third-party libs. The changes in mark_safe and mark_for_escaping are straightforward. The more tricky part is to handle correctly objects that implement __html__. Historically escape() has escaped SafeData. Even if that doesn't seem a good behavior, changing it would create security concerns. Therefore support for __html__() was only added to conditional_escape() where this concern doesn't exist. Then using conditional_escape() instead of escape() in the Django template engine makes it understand data escaped by other libraries. Template filter |escape accounts for __html__() when it's available. |force_escape forces the use of Django's HTML escaping implementation. Here's why the change in render_value_in_context() is safe. Before Django 1.7 conditional_escape() was implemented as follows: if isinstance(text, SafeData): return text else: return escape(text) render_value_in_context() never called escape() on SafeData. Therefore replacing escape() with conditional_escape() doesn't change the autoescaping logic as it was originally intended. This change should be backported to Django 1.7 because it corrects a feature added in Django 1.7. Thanks mitsuhiko for the report.
2014-12-27Fixed an inconsistency introduced in 547b1810.Aymeric Augustin
mark_safe and mark_for_escaping should have been kept similar. On Python 2 this change has no effect. On Python 3 it fixes the use case shown in the regression test for mark_for_escaping, which used to raise a TypeError. The regression test for mark_safe is just for completeness.
2014-12-27Fixed #24000 -- Corrected contrib.sites default site creation in a multiple ↵Tim Graham
database setup.
2014-12-27Forward-ported release note for 322560489Claude Paroz
2014-12-27Fixed #14180 -- Prevented unneeded index creation on MySQL-InnoDBClaude Paroz
Thanks zimnyx for the report and Simon Charette, Tim Graham for the reviews.
2014-12-27Fixed #23753 -- Added a suite of SQL FunctionsJosh Smeaton
Added functions and tests Added docs and more tests Added TextField converter to mysql backend Aliased Value as V in example docs and tests Removed unicode_compatible in example Fixed console emulation in examples
2014-12-26Removed an unnecessary models file in the admin_scripts tests.Tim Graham
2014-12-26Replaced sqlall in some bash_completion/admin_scripts tests.Tim Graham
sqlall will be removed in Django 1.9, so now's a good time to remove its usage where it's not important.
2014-12-26Clarified custom header instructions in tutorial 2.Collin Anderson
2014-12-26Fixed #24054 -- Enabled sqlsequencereset for apps with migrations.Tim Graham
2014-12-26Removed obsolete item from deprecation timeline.Tim Graham
Initial SQL data will be removed in Django 1.9 so changes to it aren't relevant.
2014-12-26Fixed #23346 -- Fixed lazy() to lookup methods on the real object, not ↵Gavin Wahl
resultclasses. Co-Authored-By: Rocky Meza <rmeza@fusionbox.com>
generated by cgit v1.3 (git 2.53.0) at 2026-08-31 16:14:05 +0000