[Python-Dev] when to fix cross-version bugs? (original) (raw)
Brian Curtin brian at python.org
Fri Sep 6 17:29:00 CEST 2013
- Previous message: [Python-Dev] when to fix cross-version bugs?
- Next message: [Python-Dev] when to fix cross-version bugs?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
- Previous message: [Python-Dev] when to fix cross-version bugs?
- Next message: [Python-Dev] when to fix cross-version bugs?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]