Triaging Python tickets: Difference between revisions

Line 7:

== Overview ==

[http://docs.python.org/devguide/triaging.html This section of the CPython developer guide] details triaging tickets. Please note that any registered user can comment on a ticket, but one must have "Developer" rights on the [http://bugs.python.org/ issue tracker] to update ticket fields.

[http://docs.python.org/devguide/triaging.html This section of the CPython developer guide] details triaging tickets. Please note that any registered user can comment on a ticket, but one must have "Developer" rights on the [http://bugs.python.org/ issue tracker] to update certain ticket fields.

If you don't have Developer rights, don't worry! Leave detailed comments on a ticket, and everyone on the [http://docs.python.org/devguide/triaging.html#nosy-list nosy list] will get an email. With your triage comments, you've greatly increased the chance that someone ~~who can update the fields~~ will ~~review your comments and~~ move the ticket forward.

If you don't have Developer rights, don't worry! Leave detailed comments on a ticket, and everyone on the [http://docs.python.org/devguide/triaging.html#nosy-list nosy list] will get an email. With your triage comments, you've greatly increased the chance that someone will move the ticket forward.

Also, if you do this for a while, you'll get Developer rights so you can make the ticket field changes yourself!

Line 73:

jesstess, thanks for your patch and tests!

The docstring for <code>parse_request</code> needs to be updated as part of this ~~changes~~.

The docstring for <code>parse_request</code> needs to be updated as part of this change.

Other than that, the patch looks correct from my inspection, applies cleanly, and implements a straightforward solution.