OOPS report model and default allocation/[de]serialization.
Project description
Copyright (c) 2011, Canonical Ltd
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
The oops project provides an in-memory model and basic serialisation, deserialisation and allocation of OOPS reports. An OOPS report is a report about something going wrong in a piece of software… thus, an ‘oops’ :)
This core package is rarely used directly: most programs or services that want to generate OOPS reports will do so via a framework specific adapter (e.g. python-oops_wsgi).
Dependencies
Python 2.6+
Testing Dependencies
subunit (http://pypi.python.org/pypi/python-subunit) (optional)
testtools (http://pypi.python.org/pypi/testtools)
Usage
Coming soon.
Installation
Either run setup.py in an environment with all the dependencies available, or add the working directory to your PYTHONPATH.
Development
Upstream development takes place at https://launchpad.net/python-oops. To setup a working area for development, if the dependencies are not immediately available, you can use ./bootstrap.py to create bin/buildout, then bin/py to get a python interpreter with the dependencies available.
To run the tests use the runner of your choice, the test suite is oops.tests.test_suite.
For instance:
$ bin/py -m testtools.run oops.tests.test_suite
