summaryrefslogtreecommitdiff
path: root/setup.py
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-12-10 15:54:43 +0000
committerChris McDonough <chrism@agendaless.com>2009-12-10 15:54:43 +0000
commit29f5c1a101802e0ba66d72195fbe4e9d340a96a0 (patch)
tree83f40864db4d6a8859e2ea6ef1bb1e8d6b359226 /setup.py
parent09bbfc5279971f5dfeadb514591b978edeeaa820 (diff)
downloadpyramid-29f5c1a101802e0ba66d72195fbe4e9d340a96a0.tar.gz
pyramid-29f5c1a101802e0ba66d72195fbe4e9d340a96a0.tar.bz2
pyramid-29f5c1a101802e0ba66d72195fbe4e9d340a96a0.zip
- Added a "Special Exceptions" section to the "Views" narrative
documentation chapter explaining the effect of raising ``repoze.bfg.exceptions.NotFound`` and ``repoze.bfg.exceptions.Forbidden`` from within view code. - When the ``repoze.bfg.exceptions.NotFound`` or ``repoze.bfg.exceptions.Forbidden`` error is raised from within a custom root factory or the ``factory`` of a route, the appropriate response is now sent to the requesting user agent (the result of the notfound view or the forbidden view, respectively). When these errors are raised from within a root factory, the ``context`` passed to the notfound or forbidden view will be ``None``. Also, the request will not be decorated with ``view_name``, ``subpath``, ``context``, etc. as would normally be the case if traversal had been allowed to take place.
Diffstat (limited to 'setup.py')
0 files changed, 0 insertions, 0 deletions