From 6ecdbc409d2109a9e7fc5367c64067f0400f07cc Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Mon, 22 Jun 2009 00:12:45 +0000 Subject: - Adding ``*path_info`` to a route no longer changes the PATH_INFO for a request that matches using URL dispatch. This feature was only there to service the ``repoze.bfg.wsgi.wsgiapp2`` decorator and it did it wrong; use ``*subpath`` instead now. - The interface generation performed for named request factories had the wrong base classes. --- CHANGES.txt | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index fe210bc34..e5cb81aa9 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -160,6 +160,11 @@ Backwards Incompatibilities (and sending a new request event) within the router (it used to be performed afterwards). +- Adding ``*path_info`` to a route no longer changes the PATH_INFO for + a request that matches using URL dispatch. This feature was only + there to service the ``repoze.bfg.wsgi.wsgiapp2`` decorator and it + did it wrong; use ``*subpath`` instead now. + Bug Fixes --------- @@ -193,13 +198,6 @@ Documentation - Updated Routes bfgwiki2 tutorial to reflect the fact that context factories are now no longer used. -Internal --------- - -- Make Routes mapper responsible for doing magic to fix up PATH_INFO - and SCRIPT_NAME when a ``path_info`` key exists in the matchdict. - This used to be done in the traverser, which made no sense. - 0.9.1 (2009-06-02) ================== -- cgit v1.2.3