Anonymous user
Triaging Python tickets: Difference between revisions
no edit summary
imported>Jesstess No edit summary |
imported>Jesstess No edit summary |
||
Line 13:
Often, someone will report a bug, but nobody will want to work on a patch for it until the bug is confirmed. Thus, confirming a bug is a big step towards getting it fixed.
===
If you '''can''' reproduce the bug:
Line 19:
# Say that you can reproduce the bug.
# Reiterate what you expected to happen, and what actually happened.
# Enumerate the steps you took to reproduce the problem.
## include a complete transcript, including the commands you ran, Python code you entered at the interpreter, tracebacks, etc. If the output is very long, for readability, attach it to the ticket instead of putting it directly in the comment.
## Attach a short, standalone program that reproduces the bug to the ticket. This will be a helpful basis for writing test cases.▼
# List all versions of Python in which the bug was and wasn't present for you.
# List all operating systems on which the bug was and wasn't present for you.
▲# Attach a short, standalone program that reproduces the bug to the ticket. This will be a helpful basis for writing test cases.
If you '''can't''' reproduce the bug:
Line 30 ⟶ 31:
# List all versions of Python in which the bug wasn't present for you.
# List all operating systems on which the bug wasn't present for you.
=== Example review ===
<blockquote>
jesstess, thanks for your bug report!<br />
<br />
I was able to reproduce the issue on both the default branch and in Python 3.4. I couldn't reproduce on 3.3, so this looks like a regression. I tested on OSX 10.8.4 but I believe this bug exists on all operating systems.<br />
<br />
I've attached a short script as a reproducer. The expected output is for it to print <code>42</code>, but it raises a <code>ValueError</code>.
</blockquote>
| |||