summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2012-03-18 18:15:32 -0400
committerChris McDonough <chrism@plope.com>2012-03-18 18:15:32 -0400
commit5cccad104522cb5b8de0e683ea3a1d5bad91d518 (patch)
tree312c5c6804e7414586b3f4449b0c4de9ff9acea2 /CHANGES.txt
parentac7d27dfb97bf887f8688264187db4a6c7be18ff (diff)
downloadpyramid-5cccad104522cb5b8de0e683ea3a1d5bad91d518.tar.gz
pyramid-5cccad104522cb5b8de0e683ea3a1d5bad91d518.tar.bz2
pyramid-5cccad104522cb5b8de0e683ea3a1d5bad91d518.zip
explain
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt9
1 files changed, 6 insertions, 3 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index d52c8d479..4befd2ecc 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -4,9 +4,12 @@ Next release
Bug Fixes
---------
-- When ``pyramid.wsgi.wsgiapp2`` calls the downstream WSGI app, the
- app's environ will no longer have (deprecated and potentially misleading)
- ``bfg.routes.matchdict`` or ``bfg.routes.route`` keys in it.
+- When ``pyramid.wsgi.wsgiapp2`` calls the downstream WSGI app, the app's
+ environ will no longer have (deprecated and potentially misleading)
+ ``bfg.routes.matchdict`` or ``bfg.routes.route`` keys in it. A symptom of
+ this bug would be a ``wsgiapp2``-wrapped Pyramid app finding the wrong view
+ because it mistakenly detects that a route was matched when, in fact, it
+ was not.
1.3b3 (2012-03-17)
==================