summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2010-09-15 00:16:54 +0000
committerChris McDonough <chrism@agendaless.com>2010-09-15 00:16:54 +0000
commit2d79938483a98ce293f533d5258dbdc85b2d59a8 (patch)
tree72421c729d4ee874f7e0083c39fe8171b0376c83 /CHANGES.txt
parentb81374bf0295b1fb2e5b094f5fc64a7748be703c (diff)
downloadpyramid-2d79938483a98ce293f533d5258dbdc85b2d59a8.tar.gz
pyramid-2d79938483a98ce293f533d5258dbdc85b2d59a8.tar.bz2
pyramid-2d79938483a98ce293f533d5258dbdc85b2d59a8.zip
Features
-------- - Compatibility with WebOb 1.0. Requirements ------------ - Now requires WebOb >= 1.0. Backwards Incompatibilities --------------------------- - Due to changes introduced WebOb 1.0, the ``repoze.bfg.request.make_request_ascii`` event subscriber no longer works, so it has been removed. This subscriber was meant to be used in a deployment so that code written before BFG 0.7.0 could run unchanged. At this point, such code will need to be rewritten to expect Unicode from ``request.GET``, ``request.POST`` and ``request.params`` or it will need to be changed to use ``request.str_POST``, ``request.str_GET`` and/or ``request.str_params`` instead of the non-``str`` versions of same, as the non-``str`` versions of the same APIs always now perform decoding to Unicode.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt25
1 files changed, 25 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 695aca255..9dbb5a0cb 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -8,6 +8,31 @@ Bug Fixes
``set_notfound_view`` or ``set_forbidden_view`` APIs, the context
sent to the view was incorrect (could be ``None`` inappropriately).
+Features
+--------
+
+- Compatibility with WebOb 1.0.
+
+Requirements
+------------
+
+- Now requires WebOb >= 1.0.
+
+Backwards Incompatibilities
+---------------------------
+
+- Due to changes introduced WebOb 1.0, the
+ ``repoze.bfg.request.make_request_ascii`` event subscriber no longer
+ works, so it has been removed. This subscriber was meant to be used
+ in a deployment so that code written before BFG 0.7.0 could run
+ unchanged. At this point, such code will need to be rewritten to
+ expect Unicode from ``request.GET``, ``request.POST`` and
+ ``request.params`` or it will need to be changed to use
+ ``request.str_POST``, ``request.str_GET`` and/or
+ ``request.str_params`` instead of the non-``str`` versions of same,
+ as the non-``str`` versions of the same APIs always now perform
+ decoding to Unicode.
+
Errata
------