Changes between Version 40 and Version 41 of BackwardsIncompatibleChanges

Timestamp:

Nov 26, 2005, 4:44:42 PM (19 years ago)

Author:

Adrian Holovaty

Comment:

Added "Changed the way custom template tags and filters are registered"

BackwardsIncompatibleChanges

@@ -1 +1 @@
 = Backwards-incompatible changes =
 
-As Django is still in pre-release mode, we haven't yet committed to maintaining backwards compatibility in any APIs. Although we're keeping such changes to a minimum, Django developers should be acutely aware of these changes.
-
-Of course, once we reach our first official release, we'll be strongly committed to backward compatibility.
+As Django is still in pre-1.0 mode, we haven't yet committed to maintaining backwards compatibility in any APIs. Although we're keeping such changes to a minimum, Django developers should be acutely aware of these changes.
+
+Of course, once we reach 1.0, we'll be strongly committed to backward compatibility.
 
 This page lists all backwards-incompatible changes to Django so far.
@@ -9 +9 @@
 == Moved mod_python handler ==
 
-As of [169], using {{{django.core.handler}}} as a mod_python handler is deprecated. Use {{{django.core.handlers.modpython}}} instead. We will be removing {{{django.core.handler}}} for Django's first release.
+As of [169], using {{{django.core.handler}}} as a mod_python handler is deprecated. Use {{{django.core.handlers.modpython}}} instead. We will be removing {{{django.core.handler}}} for 1.0.
 
 == Changed ordering syntax ==
@@ -21 +21 @@
 {{{order_by=['foo', '-bar']}}}
 
-The old syntax is deprecated, and we'll stop supporting it for Django's first release.
+The old syntax is deprecated, and we'll stop supporting it for 1.0.
 
 == Refactored meta.py ==
@@ -37 +37 @@
 {{{edit_inline=meta.TABULAR}}}
 
-We'll stop supporting the old syntax for Django's first release.
+We'll stop supporting the old syntax for 1.0.
 
 == Changed admin log to store primary keys as TEXT fields, not INTEGER fields ==
@@ -366 +366 @@
 COMMIT;
 }}}
+
+== Changed the way custom template tags and filters are registered ==
+
+As of [], we changed the way custom template tags and filters are registered. If you've written custom template tags or filters, you'll need to make a small change to the way they're registered.
+
+Old way:
+{{{
+from django.core import template
+
+template.register_filter('lower', lower, False)
+template.register_tag('current_time', do_current_time)
+}}}
+
+New way:
+
+{{{
+from django.core import template
+
+register = template.Library()
+register.filter('lower', lower)
+register.tag('current_time', do_current_time)
+}}}
+
+A new decorator syntax is also supported.
+
+See [http://www.djangoproject.com/documentation/templates_python/#writing-custom-template-filters Writing custom template filters] and [http://www.djangoproject.com/documentation/templates_python/#writing-custom-template-tags Writing custom template tags] for full documentation.