[Python-Dev] when to fix cross-version bugs? (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Sat Sep 7 13:01:36 CEST 2013

On 7 Sep 2013 02:43, "Ethan Furman" <ethan at stoneleaf.us> wrote:

On 09/06/2013 07:51 AM, Ethan Furman wrote:

What guidelines determine when a bug is fixed in previous versions? On 09/06/2013 08:29 AM, Brian Curtin wrote: If it's a bug in that version and the version is accepting bug fixes, i.e., not in security mode, go for it. This includes crossing the 2/3 boundary if applicable. On 09/06/2013 08:31 AM, R. David Murray wrote: The basic guideline is: we try very hard not to break currently working code in a maintenance release. Making that decision very much depends on the details of each individual case. [so] it probably doesn't have much positive impact if it does get backported, so is it worth the (small) chance of breaking someone's code? And they say never go to the elves for advice! ;)

Fixes that risk breaking current doctests are rarely worth backporting, so in this case, I'd say only fixing it in 3.4 is the better option.

Definitely the kind of borderline case worth asking about, though :)

Cheers, Nick.

-- Ethan

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130907/d8ca9aff/attachment.html>

More information about the Python-Dev mailing list