summaryrefslogtreecommitdiff
path: root/docs/whatsnew-1.1.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/whatsnew-1.1.rst')
-rw-r--r--docs/whatsnew-1.1.rst23
1 files changed, 23 insertions, 0 deletions
diff --git a/docs/whatsnew-1.1.rst b/docs/whatsnew-1.1.rst
index 3252cba22..d83582dee 100644
--- a/docs/whatsnew-1.1.rst
+++ b/docs/whatsnew-1.1.rst
@@ -370,6 +370,29 @@ Deprecations and Behavior Differences
use convert code using this feature to use a BeforeRender event als
:ref:`beforerender_event`.
+- In Pyramid 1.0, the :class:`pyramid.events.subscriber` directive behaved
+ contrary to the documentation when passed more than one interface object to
+ its constructor. For example, when the following listener was registered::
+
+ @subscriber(IFoo, IBar)
+ def expects_ifoo_events_and_ibar_events(event):
+ print event
+
+ The Events chapter docs claimed that the listener would be registered and
+ listening for both ``IFoo`` and ``IBar`` events. Instead, it registered an
+ "object event" subscriber which would only be called if an IObjectEvent was
+ emitted where the object interface was ``IFoo`` and the event interface was
+ ``IBar``.
+
+ The behavior now matches the documentation. If you were relying on the
+ buggy behavior of the 1.0 ``subscriber`` directive in order to register an
+ object event subscriber, you must now pass a sequence to indicate you'd
+ like to register a subscriber for an object event. e.g.::
+
+ @subscriber([IFoo, IBar])
+ def expects_object_event(object, event):
+ print object, event
+
Dependency Changes
------------------