Changes between Version 52 and Version 53 of BackwardsIncompatibleChanges

Timestamp:

Nov 27, 2005, 4:09:10 PM (18 years ago)

Author:

Adrian Holovaty

Comment:

Added "Added support for non-named groups in URLconf regular expressions"

BackwardsIncompatibleChanges

@@ -469 +469 @@
 === Templates ===
 
-Templates that are included in another template using {{{{% include %}}}} or {{{{% ssi %}}}}, or extend a template using {{{{% extends %}}}}, must explicitly {{{{% load %}}}} all libraries they need for their tags and filters. Some templates may have worked in the past due to previous requests registering tags : this will no longer work.  
+Templates that are included in another template using {{{{% include %}}}} or {{{{% ssi %}}}}, or extend a template using {{{{% extends %}}}}, must explicitly {{{{% load %}}}} all libraries they need for their tags and filters. Some templates may have worked in the past due to previous requests registering tags : this will no longer work.
+
+== Added support for non-named groups in URLconf regular expressions ==
+
+As of [1470], Django URLconfs support non-named groups in URLconf regular expressions. This means you no longer have to specify the name of each group.
+
+For example, this old syntax:
+{{{
+(r'^(?P<item_id>\d{1,3})/$', 'foo.item_detail'),
+}}}
+
+Can be shortened to this syntax:
+{{{
+(r'^(\d{1,3})/$', 'foo.item_detail'),
+}}}
+
+The algorithm it follows is: If there are any named groups, it will use those, ignoring all non-named groups. Otherwise, it will pass all non-named groups as positional arguments. In both cases, it will pass any {{{extra_kwargs}}} as keyword arguments.
+
+The old syntax (named groups) still works. Use that in cases where you can't (or don't want to) couple the order of URL parameters with the order of your view function arguments.
+
+There are two small backwards-incompatibilities about this change:
+
+ * If you've written custom middleware that implements {{{process_view()}}}, you'll need to change it so it takes {{{view_args}}} and {{{view_kwargs}}} arguments instead of {{{param_dict}}}:
+
+   {{{
+   def process_view(self, request, view_func, view_args, view_kwargs)
+   }}}
+
+ * On the off chance you have legacy URLconfs that have NO captured items but DO use capturing parenthesis (which until now would have had no effect), you'll need to either change your view code to accept the captured values, or uncapture them.