This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients lars.gustaebel, paul.moore, pitrou
Date 2009-11-18.20:54:24
SpamBayes Score 1.9436067e-08
Marked as misclassified No
Message-id <1258577679.3476.18.camel@localhost>
In-reply-to <1258577522.54.0.99821788428.issue7341@psf.upfronthosting.co.za>
Content
> I have always tried to be very conservative with backporting stuff that
> is not clearly a bugfix but alters any kind of behaviour. I am always
> very concerned about compatibility, especially if code has been around
> for as long as this code has.
> But as I don't want to waste anybody's time with a lengthy discussion,
> just say a word and I apply it to 2.6 and 3.1 as well ;-)

What if I say chocolate?
Regardless, I think you should backport it at least to 3.1, and that it
makes sense to backport it to 2.6 too.
History
Date User Action Args
2009-11-18 20:54:26pitrousetrecipients: + pitrou, paul.moore, lars.gustaebel
2009-11-18 20:54:24pitroulinkissue7341 messages
2009-11-18 20:54:24pitroucreate