Permalink
Browse files

prep for 1.1a2

  • Loading branch information...
1 parent e7e35e8 commit cc85e7a96ccbb1671514adb1a1b1992fd1f02461 @mcdonc mcdonc committed Jun 22, 2011
Showing with 34 additions and 8 deletions.
  1. +5 −5 CHANGES.txt
  2. +1 −1 RELEASING.txt
  3. +1 −1 docs/conf.py
  4. +26 −0 docs/whatsnew-1.1.rst
  5. +1 −1 setup.py
View
@@ -1,12 +1,12 @@
-Next release
-============
+1.1a2 (2011-06-22)
+==================
Bug Fixes
---------
- 1.1a1 broke Akhet by not providing a backwards compatibility import shim
for ``pyramid.paster.PyramidTemplate``. Now one has been added, although a
- deprecation warning is raised.
+ deprecation warning is emitted when Akhet imports it.
- If multiple specs were provided in a single call to
``config.add_translation_dirs``, the directories were inserted into the
@@ -20,8 +20,8 @@ Backwards Incompatibilities
- The pyramid Router attempted to set a value into the key
``environ['repoze.bfg.message']`` when it caught a view-related exception
- for backwards compatibility with :mod:`repoze.bfg` during error handling.
- It did this by using code that looked like so::
+ for backwards compatibility with applications written for ``repoze.bfg``
+ during error handling. It did this by using code that looked like so::
# "why" is an exception object
try:
View
@@ -13,7 +13,7 @@ Releasing Pyramid
communicate with contributors).
- Copy relevant changes (delta bug fixes) from CHANGES.txt to
- docs/whatsnew-X.X.
+ docs/whatsnew-X.X (if it's a major release).
- Make sure docs render OK::
View
@@ -93,7 +93,7 @@ def nothing(*arg):
# other places throughout the built documents.
#
# The short X.Y version.
-version = '1.1a1'
+version = '1.1a2'
# The full version, including alpha/beta/rc tags.
release = version
View
@@ -199,6 +199,32 @@ Backwards Incompatibilities
pyramid.httpexceptions.HTTPFound(location='http//foo')`` (the latter will
of course continue to work).
+- The pyramid Router attempted to set a value into the key
+ ``environ['repoze.bfg.message']`` when it caught a view-related exception
+ for backwards compatibility with applications written for :mod:`repoze.bfg`
+ during error handling. It did this by using code that looked like so::
+
+ # "why" is an exception object
+ try:
+ msg = why[0]
+ except:
+ msg = ''
+
+ environ['repoze.bfg.message'] = msg
+
+ Use of the value ``environ['repoze.bfg.message']`` was docs-deprecated in
+ Pyramid 1.0. Our standing policy is to not remove features after a
+ deprecation for two full major releases, so this code was originally slated
+ to be removed in Pyramid 1.2. However, computing the
+ ``repoze.bfg.message`` value was the source of at least one bug found in
+ the wild (https://github.com/Pylons/pyramid/issues/199), and there isn't a
+ foolproof way to both preserve backwards compatibility and to fix the bug.
+ Therefore, the code which sets the value has been removed in this release.
+ Code in exception views which relies on this value's presence in the
+ environment should now use the ``exception`` attribute of the request
+ (e.g. ``request.exception[0]``) to retrieve the message instead of relying
+ on ``request.environ['repoze.bfg.message']``.
+
Deprecations and Behavior Differences
-------------------------------------
View
@@ -53,7 +53,7 @@
install_requires.append('simplejson')
setup(name='pyramid',
- version='1.1a1',
+ version='1.1a2',
description=('The Pyramid web application development framework, a '
'Pylons project'),
long_description=README + '\n\n' + CHANGES,

0 comments on commit cc85e7a

Please sign in to comment.