From 7eb4adc19acd98c10fa7d5f4f63b6ed1fe82b234 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 21 Nov 2010 00:37:42 -0500 Subject: prep for 1.0a4 --- CHANGES.txt | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index aee0fae2f..84b103e65 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,5 +1,5 @@ -Next release -============ +1.0a4 (2010-11-21) +================== Features -------- @@ -8,10 +8,11 @@ Features in the pattern, instead of immediately following a ``/``. - URL Dispatch now uses the form ``{marker}`` to denote a replace marker in - the route pattern instead of ``:marker``. The old syntax is still backwards - compatible and accepted. The new format allows a regular expression for that - marker location to be used instead of the default ``[^/]+``, for example - ``{marker:\d+}`` is now valid to require the marker to be digits. + the route pattern instead of ``:marker``. The old colon-style marker syntax + is still accepted for backwards compatibility. The new format allows a + regular expression for that marker location to be used instead of the + default ``[^/]+``, for example ``{marker:\d+}`` is now valid to require the + marker to be digits. - Add a ``pyramid.url.route_path`` API, allowing folks to generate relative URLs. Calling ``route_path`` is the same as calling @@ -62,7 +63,7 @@ Bug Fixes ASCII string rather than being passed along to downstream code as a convenience to the user and to prevent puzzling second-order failures from cropping up (all failures will occur within ``pyramid.traversal.traverse`` - rather than later down the line as the result of calling + rather than later down the line as the result of calling e.g. ``traversal_path``). Backwards Incompatibilities -- cgit v1.2.3