Triaging Python tickets: Difference between revisions

 

== Verifying bugs ==

 

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.

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>

 

== Reviewing patches ==

 

CPython committers are really busy, and they won't typically try to merge a patch until someone else has reviewed it. Thus, reviewing a patch is a big step towards getting it merged.

After the docstring is updated, I think this is ready for a commit review!

</blockquote>

 

== Reviewing documentation patches ==

 

Documentation patches have some different steps from code patches. They don't generally require accompanying tests, and they should be inspected visually for correctness.

The docs build cleanly with the patch. I visually inspected the changes in the built HTML docs and they look good. I also ran the modified example code from the docs and confirmed that it runs as expected.

</blockquote>

 

== Finding tickets to triage ==