git-blame for stacktraces
Project description
git-stacktrace is designed to make it easy to figure out which commit caused a given stacktrace.
git-stacktrace looks for:
commits in given range that touched files in the stacktrace
commits in given range that added/removed code present the stacktrace
Development
Run tests with: tox
Installation
$ pip install git_stacktrace
Usage
For the CLI see: git stacktrace -h
For the Python API see: git_stacktrace/api.py
Examples
Example output:
$ git stacktrace --since=1.day < trace Traceback: File "webapp/framework/resource.py", line 72, in _call result = getattr(self, method_name)() File "webapp/resources/interests_resource.py", line 232, in get if self.options['from_navigate'] == "true": commit da39a3ee5e6b4b0d3255bfef95601890afd80709 Commit Date: Tue, 19 Jul 2016 14:18:08 -0700 Author: John Doe <johndoe@pinterest.com> Subject: break interest resource Link: https://example.com/D1000 files: - webapp/resources/interests_resource.py lines added: - "if self.options['from_navigate'] == "true":"
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
git-stacktrace-0.4.1.tar.gz
(14.8 kB
view hashes)