The backtracepython  package is available in pip  or at .

Supported Platforms

The backtracepython  package supports both Python 2 and 3.

Basic Usage

import backtracepython as bt
    endpoint="", token="51cc8e69c5b62fa8c72dc963e730f1e8eacbd243aeafc35d08d05ded9a024121"

Sending Reports from Unhandled Exceptions

By default, the backtracepython module will automatically capture unhandled exceptions and create and send error reports from them.  This behavior can be adjusted with the disable_global_handler  option to bt.initialize (see below).

Sending Reports Manually

You can also send error reports manually within code.  However, in order to get a correct callstack and source code context, you must send an error with a python exception context.  To do this, you can raise a python exception then immediately send a report via the send_last_exception call.  A simple example:

    raise Exception("This report was sent manually.")




  • endpoint  - Required. Example: .  Sets the HTTP/HTTPS endpoint that error reports will be sent to. 

  • token  -  Required. Example: 51cc8e69c5b62fa8c72dc963e730f1e8eacbd243aeafc35d08d05ded9a024121  Sets the token that will be used for authentication when sending an error report. 

  • attributes  - Dictionary that contains additional attributes to be sent along with every error report. These can be overridden on an individual report with report.set_attribute  Example: { 'application': "ApplicationName", 'serverId': "foo" }  

  • timeout  - Defaults to 4. Maximum amount of seconds to wait for error report processing and sending before concluding it failed. 

  • debug_backtrace - Defaults to False . Set to True to have an error during collecting the report raise an exception, and to print some debugging information to stderr. 

  • disable_global_handler - Defaults to False. If this is False  this module will insert itself in the sys.excepthook chain and report those errors automatically before re-raising the exception. Set to True  to disable this. Note that in this case the only way error reports will be reported is if you manually create and send them. 

  • context_line_count  - Defaults to 200 . When an error is reported, this many lines above and below each stack function are included in the report. 

  • tab_width  - Defaults to 8.  If there are any hard tabs in the source code, it is unclear how many spaces they should be indented to correctly display the source code. Therefore the error report can override this number to specify how many spaces a hard tab should be represented by when viewing source code. 


Create a report object that you can later choose whether or not to send.

This may be useful to track something like a request.

report.set_attribute(key, value) 

Adds an attribute to a specific report. Valid types for value are str, float, int, and bool.

Attributes are indexed and searchable. See also addAnnotation.


Adds all key-value pairs of dict into the report recursively.

report.set_annotation(key, value) 

Adds an annotation to a specific report. Annotations, unlike attributes, are not indexed and searchable. However, they are available for inspection when you view a specific report.

  • key - String which is the name of the annotation.

  • value - Any type which is JSON-serializable.


Adds all key-value pairs of dict into the report.

report.set_exception(ExceptionType, exception, traceback)

 is an Error object. Backtrace will extract information from this object such as the error message and stack trace and send this information along with the report.


This is the same as report.set_exception(*sys.exc_info())


Adds a timestamped log message to the report. Log output is available when you view a report.


Sends the error report to the endpoint specified in initialize.


  • attributes  - dictionary of attributes to add to the report. See report.set_dict_attributes

  • annotations  - dictionary of annotations to add to the report. See report.set_dict_annotations



This module supports Python 2, Python 3, and PyPy.

python -m pip install backtracepython


To run the test suite:

python test

Since all of these implementations of Python are supported, be sure to run the test suite with all of them:

  • Python 2

  • Python 3

  • PyPy

Publishing to PyPI

  1. Make sure all tests pass (see above).

  2. Update version number in backtracepython module.

  3. Tag the version in git.

python2 bdist_wheel --universal
twine upload dist/*
Did this answer your question?