RetroSearch Browse

Fri Sep 6 18:18:12 CEST 2013 · https://mail.python.org/pipermail/python-dev/2013-September/128396.html

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!  ;)

--
~Ethan~

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-September/128396.html below:

[Python-Dev] when to fix cross-version bugs?