Author loewis
Recipients benjamin.peterson, christian.heimes, georg.brandl, loewis, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-09.06:59:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <50235FC1.5070103@v.loewis.de>
In-reply-to <1344494154.97.0.295974020678.issue12834@psf.upfronthosting.co.za>
Content
> Since the next release of 3.2 is the *last* release of 3.2, yet it
> will remain supported by distros well beyond that, yes, I think this
> should block the final 3.2 release.

But the same will be true for any other bug that 3.2 has. If they
don't get fixed now, they will remain unfixed. Should we therefore
delay the last release of 3.2 until all bugs in it are fixed?

The consequence instead should be that people experiencing this
bug will have to move to Python 3.3 to get it fixed. Since it only
affects NumPy users (AFAICT), and then only those who use tobytes,
I wouldn't consider this bug even critical.
History
Date User Action Args
2012-08-09 06:59:18loewissetrecipients: + loewis, georg.brandl, ncoghlan, pitrou, vstinner, christian.heimes, benjamin.peterson, skrah, meador.inge, python-dev
2012-08-09 06:59:17loewislinkissue12834 messages
2012-08-09 06:59:17loewiscreate