Merge lp:~lifeless/python-oops-datedir-repo/0.0.9 into lp:python-oops-datedir-repo
Proposed by
Robert Collins
Status: | Merged |
---|---|
Merged at revision: | 18 |
Proposed branch: | lp:~lifeless/python-oops-datedir-repo/0.0.9 |
Merge into: | lp:python-oops-datedir-repo |
Diff against target: |
192 lines (+83/-7) 6 files modified
NEWS (+11/-0) README (+1/-1) oops_datedir_repo/__init__.py (+1/-1) oops_datedir_repo/repository.py (+16/-3) oops_datedir_repo/tests/test_repository.py (+53/-1) setup.py (+1/-1) |
To merge this branch: | bzr merge lp:~lifeless/python-oops-datedir-repo/0.0.9 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
j.c.sackett (community) | Approve | ||
Review via email: mp+78793@code.launchpad.net |
Description of the change
Prep for amqp in oops-tools: Support for using ids supplied to the publisher - useful for oops-amqp which shows an id to users before the disk storage code sees the oops, and permit passing the filename chosen for storage forward, which lets the oops-tools publisher put the filename in to the django model.
To post a comment you must log in.
I think it would be clearer if self.inherit_id left the value of report[id] alone::
tmp_id = 'OOPS-%s' % md5hash
if not self.inherit or report.get(id) is None:
report[id] = tmp_id
"return original_id or report['id']" looks like it's meant to return the canonical oops-id, but when original_id is non-None, won't it be the same as report['id']?