Skip to main content

OOPS disk serialisation and repository management.

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 Lesser General Public License as published by the Free Software Foundation, version 3 only.

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 Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this program. If not, see <>. GNU Lesser General Public License version 3 (see the file LICENSE).

This is a component of the python-oops project: An OOPS report is a report about something going wrong in a piece of software… thus, an ‘oops’ :)

This package provides disk storage, management, and a serialisation format for OOPSes stored in the repository. Programs or services that are generating OOPS reports need this package or other similar ones, if they want to persist the reports.



oops_datedir_repo is an extension package for the oops package.

The DateDirRepo class provides an OOPS publisher (DateDirRepo.publish) which will write OOPSes into the repository.

Retrieving OOPSes can be done by using the low level serializer_rfc822 functions : an OOPS report can be written to a disk file via the serializer_rfc822.write() function, and read via the matching read() function.

The uniquefileallocator module is used by the repository implementation and provides a system for allocating file names on disk.

Typical usage:

>>> config = oops.Config()
>>> with fixtures.TempDir() as tempdir:
...    repo = oops_datedir_repo.DateDirRepo('/tmp/demo', 'servername')
...    config.publishers.append(repo.publish)
...    ids = config.publish({'oops': '!!!'})

For more information see the oops package documentation or the api docs.


Either run in an environment with all the dependencies available, or add the working directory to your PYTHONPATH.


Upstream development takes place at To setup a working area for development, if the dependencies are not immediately available, you can use ./ 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_datedir_repo.tests.test_suite.

For instance:

$ bin/py -m oops_datedir_repo.tests.test_suite

If you have testrepository you can run the tests with that:

$ testr run

Project details

Release history Release notifications

History Node


History Node


History Node


History Node


History Node


This version
History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


Download files

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

Filename, size & hash SHA256 hash help File type Python version Upload date
oops_datedir_repo-0.0.19.tar.gz (14.1 kB) Copy SHA256 hash SHA256 Source None Sep 19, 2012

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging CloudAMQP CloudAMQP RabbitMQ AWS AWS Cloud computing Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page