summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-11-19 00:34:21 +0000
committerChris McDonough <chrism@agendaless.com>2009-11-19 00:34:21 +0000
commitde821203ffe585cb63b19bcfc238503994f15725 (patch)
tree3b98292cf2462962c8485db99e6ca42a4997aca0 /CHANGES.txt
parent57251c6aab46bd87b88db63881e125f86b79befe (diff)
downloadpyramid-de821203ffe585cb63b19bcfc238503994f15725.tar.gz
pyramid-de821203ffe585cb63b19bcfc238503994f15725.tar.bz2
pyramid-de821203ffe585cb63b19bcfc238503994f15725.zip
Checkpoint: move most zcml route and view directive tests to test_configuration.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt27
1 files changed, 24 insertions, 3 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index e4c4420e9..bb09e08b2 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -21,9 +21,30 @@ Internals
Backwards Incompatibilites
--------------------------
-The ``repoze.bfg.router.make_app`` callable no longer accepts the
-``authentication_policy`` nor the ``authorization_policy`` arguments.
-This feature was deprecated in version 1.0 and has been removed.
+- View registration no longer registers a
+ ``repoze.bfg.interfaces.IViewPermission`` adapter (it is no longer
+ checked by the framework; since 1.1, views have been responsible for
+ providing their own security).
+
+- The ``repoze.bfg.router.make_app`` callable no longer accepts the
+ ``authentication_policy`` nor the ``authorization_policy``
+ arguments. This feature was deprecated in version 1.0 and has been
+ removed.
+
+- Obscure: the machinery which configured views with a
+ ``request_type`` *and* a ``route_name`` would ignore the request
+ interface implied by ``route_name`` registering a view only for the
+ interface implied by ``request_type``. In the unlikely event that
+ you were trying to use these two features together, the symptom
+ would have been that views that named a ``request_type`` but which
+ were also associated with routes were not found when the route
+ matched. Now if a view is configured with both a ``request_type``
+ and a ``route_name``, an error is raised.
+
+- The ``route`` ZCML directive now no longer accepts the
+ ``request_type`` or ``view_request_type`` attributes. These
+ attributes didn't actually work in any useful way (see entry above
+ this one).
1.1 (2009-11-15)
================