Skip to main content

Zope 3 exception views

This project has been archived.

The maintainers of this project have marked this project as archived. No new releases are expected.

Project description

This packages provides Zope 3 browser views for some generic exceptions.

System Errors

System Errors are errors representing a system failure. At the application level, they are errors that are uncaught by the application and that a developer hasn’t provided a custom error view for.

Zope provides a default system error view that prints an obnoxius terse message and that sets the response status.

There is a simple view registered in ftesting.zcml which raises Exception():

>>> print(http(r"""
... GET /error.html HTTP/1.1
... """))
HTTP/1.0 500 Internal Server Error
...
  A system error occurred.
...

Another way of getting a system error is the occurrence of a system error, such as ComponentLookupError. I have registered a simple view in ftesting.zcml, too, that will raise a component lookup error. So if we call componentlookuperror.html, we should get the error message:

>>> print(http(r"""
... GET /componentlookuperror.html HTTP/1.1
... """))
HTTP/1.0 500 Internal Server Error
...
  A system error occurred.
...

CHANGES

4.0.1 (2017-05-15)

  • Fix rendering of user errors on Python 3. See issue 2.

4.0.0 (2017-05-01)

  • Add support for PyPy, and Python 3.4, 3.5 and 3.6.

  • Remove test dependency on zope.app.testing, zope.app.zcmlfiles and many others.

3.6.3 (2011-05-23)

  • Replaced an undeclared test dependency on zope.app.authentication with zope.password.

3.6.2 (2010-09-14)

  • No longer depend on zope.app.zptpage for tests.

  • Replaced dependency on zope.app.securitypolicy by zope.securitypolicy.

3.6.1 (2010-01-08)

  • Require zope.browserpage which now contains namedtemplate.

  • Fix ftesting.zcml due to zope.securitypolicy update.

  • Fix tests using a newer zope.publisher that requires zope.login.

3.6.0 (2009-05-18)

  • ISystemErrorView interface has been moved to zope.browser.interfaces, leaving BBB import here.

  • Cut dependency on zope.formlib by requiring newer version of zope.app.pagetemplate which now contains namedtemplate.

3.5.0 (2009-04-06)

  • Use new zope.authentication instead of zope.app.security.

  • Removed deprecated code and thus removed dependency on zope.deferredimport.

  • Removed old zpkg-related SETUP.cfg file.

3.4.2 (2009-01-27)

  • Substitute zope.app.zapi by direct calls to its wrapped apis. See bug 219302.

  • Fixed author email and home page.

3.4.1 (2007-10-31)

  • Resolve ZopeSecurityPolicy deprecation warning.

3.4.0 (2007-10-24)

  • Initial release independent of the main Zope tree.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

zope.app.exception-4.0.1.tar.gz (13.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

zope.app.exception-4.0.1-py2.py3-none-any.whl (18.3 kB view details)

Uploaded Python 2Python 3

File details

Details for the file zope.app.exception-4.0.1.tar.gz.

File metadata

File hashes

Hashes for zope.app.exception-4.0.1.tar.gz
Algorithm Hash digest
SHA256 6addded3f918792fd6d90946cca687e3dc7c149a558f6652f7d78cc26e8999d4
MD5 37703e9dd6f3b357bf7dc0c5b6d76760
BLAKE2b-256 1415bf30e445fde70d08f55ac66c2a9b73a75950c22c08692733580787f05111

See more details on using hashes here.

File details

Details for the file zope.app.exception-4.0.1-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for zope.app.exception-4.0.1-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 eaa85cec2e298b921f4647a23f0b541cc78c707cf3f5799fc97cb137cb89771c
MD5 b4a64a7513e3fce86d20bc3f4bfc843f
BLAKE2b-256 ba8586c3137f2a513cd8327b333567214e0cb5cbd1d840fc2d6acb0fb73565af

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page