From 04b7eae0bf933d6144f7cf9f339b9ed6153b9a0f Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Tue, 23 Aug 2011 22:55:54 -0400 Subject: add explanations --- CHANGES.txt | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index c752f8005..86ae8c49d 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -171,6 +171,33 @@ Backwards Incompatibilities instead make a separate call to the method for each callable. This change was introduced to support the ``route_prefix`` feature of include. +- It may be necessary to more strictly order configuration route and view + statements when using an "autocommitting" Configurator. In the past, it + was possible to add a view which named a route name before adding a route + with that name when you used an autocommitting configurator. For example:: + + config = Configurator(autocommit=True) + config.add_view('my.pkg.someview', route_name='foo') + config.add_route('foo', '/foo') + + The above will raise an exception when the view attempts to add itself. + Now you must add the route before adding the view:: + + config = Configurator(autocommit=True) + config.add_route('foo', '/foo') + config.add_view('my.pkg.someview', route_name='foo') + + This won't effect "normal" users, only people who have legacy BFG codebases + that used an autommitting configurator and possibly tests that use the + configurator API (the configurator returned by ``pyramid.testing.setUp`` is + an autocommitting configurator). The right way to get around this is to + use a non-autocommitting configurator (the default), which does not have + these directive ordering requirements. + +- The ``pyramid.config.Configurator.add_route`` directive no longer returns a + route object. This change was required to make route vs. view + configuration processing work properly. + Documentation ------------- -- cgit v1.2.3 From c1a179fbc713a8c8c5be19f8d327b8ced567d957 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 24 Aug 2011 00:29:42 -0400 Subject: prep for 1.2a1 --- CHANGES.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index 86ae8c49d..5e4c63df1 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,5 +1,5 @@ -Next release -============ +1.2a1 (2011-08-24) +================== Features -------- -- cgit v1.2.3 From b93af955803b3ae9dec72d6e3b0d3d3014e58b3f Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 24 Aug 2011 10:56:13 -0400 Subject: - When a ``renderers=`` argument is not specified to the Configurator constructor, eagerly register and commit the default renderer set. This permits the overriding of the default renderers, which was broken in 1.2a1 without a commit directly after Configurator construction. --- CHANGES.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'CHANGES.txt') diff --git a/CHANGES.txt b/CHANGES.txt index 5e4c63df1..e5340de4c 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,3 +1,11 @@ +Next release +============ + +- When a ``renderers=`` argument is not specified to the Configurator + constructor, eagerly register and commit the default renderer set. This + permits the overriding of the default renderers, which was broken in 1.2a1 + without a commit directly after Configurator construction. + 1.2a1 (2011-08-24) ================== -- cgit v1.2.3