CHANGES.txt | ●●●●● patch | view | raw | blame | history | |
RELEASING.txt | ●●●●● patch | view | raw | blame | history | |
docs/conf.py | ●●●●● patch | view | raw | blame | history | |
docs/whatsnew-1.1.rst | ●●●●● patch | view | raw | blame | history | |
setup.py | ●●●●● patch | view | raw | blame | history |
CHANGES.txt
@@ -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 @@ - 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: RELEASING.txt
@@ -13,7 +13,7 @@ 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:: docs/conf.py
@@ -93,7 +93,7 @@ # 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 docs/whatsnew-1.1.rst
@@ -199,6 +199,32 @@ 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 ------------------------------------- setup.py
@@ -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,