Berker Peksag added the comment: 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. ---------- nosy: +berker.peksag resolution: -> fixed stage: -> resolved status: open -> closed type: -> behavior versions: -Python 3.4 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23076> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
