summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2008-12-05 15:55:54 +0000
committerChris McDonough <chrism@agendaless.com>2008-12-05 15:55:54 +0000
commitd33f742c019afa8a5adfa889c0e02ad17b26bcf9 (patch)
tree9e9d0795a80a5d98eb36b4a94bd8ab45ffa652cb /CHANGES.txt
parentea2b46c21bcefeb85d41fc707260c885516ce483 (diff)
downloadpyramid-d33f742c019afa8a5adfa889c0e02ad17b26bcf9.tar.gz
pyramid-d33f742c019afa8a5adfa889c0e02ad17b26bcf9.tar.bz2
pyramid-d33f742c019afa8a5adfa889c0e02ad17b26bcf9.zip
Prepare for 0.5.2.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt11
1 files changed, 9 insertions, 2 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 83126b062..07ad19439 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,11 +1,18 @@
-Next release
+0.5.2 (12/5/2008)
- The component registration handler for views (functions or class
instances) now observes component adaptation annotations (see
``zope.component.adaptedBy``) and uses them before the fallback
values for ``for_`` and ``request_type``. This change does not
affect existing code insomuch as the code does not rely on these
- defaults when an annotation is set on the view (unlikely).
+ defaults when an annotation is set on the view (unlikely). This
+ means that for a new-style class you can do
+ ``zope.component.adapts(ISomeContext, ISomeRequest)`` at class
+ scope or at module scope as a decorator to a bfg view function you
+ can do ``@zope.component.adapter(ISomeContext, ISomeRequest)``.
+ This differs from r.bfg.convention inasmuch as you still need to
+ put something in ZCML for the registrations to get done; it's only
+ the defaults that will change if these declarations exist.
- Strip all slashes from end and beginning of path in clean_path
within traversal machinery.