summaryrefslogtreecommitdiff
path: root/setup.py
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2011-07-12 03:52:42 -0400
committerChris McDonough <chrism@plope.com>2011-07-12 03:52:42 -0400
commit82efa44c0d8f4b18b4f341519f54ecad68b56364 (patch)
tree3abdcf96776957aacef3c8fcba53e68186d609e2 /setup.py
parentf9896b60700ea4334f3df0a83f9b291e167b322d (diff)
downloadpyramid-82efa44c0d8f4b18b4f341519f54ecad68b56364.tar.gz
pyramid-82efa44c0d8f4b18b4f341519f54ecad68b56364.tar.bz2
pyramid-82efa44c0d8f4b18b4f341519f54ecad68b56364.zip
- Previously, If a ``BeforeRender`` event subscriber added a value via the
``__setitem__`` or ``update`` methods of the event object with a key that already existed in the renderer globals dictionary, a ``KeyError`` was raised. With the deprecation of the "add_renderer_globals" feature of the configurator, there was no way to override an existing value in the renderer globals dictionary that already existed. Now, the event object will overwrite an older value that is already in the globals dictionary when its ``__setitem__`` or ``update`` is called (as well as the new ``setdefault`` method), just like a plain old dictionary. As a result, for maximum interoperability with other third-party subscribers, if you write an event subscriber meant to be used as a BeforeRender subscriber, your subscriber code will now need to (using ``.get`` or ``__contains__`` of the event object) ensure no value already exists in the renderer globals dictionary before setting an overriding value.
Diffstat (limited to 'setup.py')
0 files changed, 0 insertions, 0 deletions