A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] when to fix cross-version bugs?Brian Curtin brian at python.org
Fri Sep 6 17:29:00 CEST 2013
On Fri, Sep 6, 2013 at 9:51 AM, Ethan Furman <ethan at stoneleaf.us> wrote:
> I recently committed a fix for unicodeobject.c so that the %d, %i, and %u
> format specifiers always output values (otherwise, in subclasses, the str()
> was used instead).
>
> Should this be fixed in 3.3 as well?
>
> What guidelines determine when a bug is fixed in previous versions?

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.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4