➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author berker.peksag
Recipients Antony.Lee, Arfrever, berker.peksag, gvanrossum, liu chang, pitrou, python-dev, thomas.nyberg
Date 2016-01-30.16:03:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454169795.64.0.0557771165776.issue23076@psf.upfronthosting.co.za>
In-reply-to
Content 
Thanks for the patch, Thomas!

> Though I've been reading the developer guide, I'm a bit unfamiliar with the process here so I'm not totally sure I'm doing this right.

You did everything right :) I just tweaked the test a bit.

> I created the patch relative to the current default branch (even though the discussion here seems to indicate it should maybe be applied going back a few versions).

Backporting a patch is (most of the time) the core developer's responsibility. However, if the patch is going to be very different in maintenance branches (let's say 2.7 for example), it would be really helpful to attach a separate patch for 2.7.
History
Date User Action Args
2016-01-30 16:03:15berker.peksagsetrecipients: + berker.peksag, gvanrossum, pitrou, Arfrever, python-dev, Antony.Lee, liu chang, thomas.nyberg
2016-01-30 16:03:15berker.peksagsetmessageid: <1454169795.64.0.0557771165776.issue23076@psf.upfronthosting.co.za>
2016-01-30 16:03:15berker.peksaglinkissue23076 messages
2016-01-30 16:03:15berker.peksagcreate