Re: Should #14930 be reopened?

2011-01-18 Thread richard . anderson
;ll get the chance, but now that the bug is reopened, it's definitely high on my priority list. Many thanks again. :) Richard Anderson pgpRecQk34BeO.pgp Description: PGP signature

Re: Should #14930 be reopened?

2011-01-18 Thread richard . anderson
On Wed, Jan 19, 2011 at 09:26:39AM +0800, Russell Keith-Magee wrote: > On Wed, Jan 19, 2011 at 5:50 AM, wrote: > > On Tue, Jan 18, 2011 at 10:23:33PM +0100, ??ukasz Rekucki wrote: > >> On 18 January 2011 20:07, ? wrote: > >> > #14930 was closed wontfix blaming a buggy version of Python (2.6.1) fo

Re: Should #14930 be reopened?

2011-01-18 Thread richard . anderson
On Tue, Jan 18, 2011 at 10:23:33PM +0100, ??ukasz Rekucki wrote: > On 18 January 2011 20:07, wrote: > > #14930 was closed wontfix blaming a buggy version of Python (2.6.1) for the > > issue. ??I've reproduced the same issue on Python 2.6.6 and on 2.7.1. > > ??I've only > > reproduced the issue o

Should #14930 be reopened?

2011-01-18 Thread richard . anderson
#14930 was closed wontfix blaming a buggy version of Python (2.6.1) for the issue. I've reproduced the same issue on Python 2.6.6 and on 2.7.1. I've only reproduced the issue on Django 1.2.3, however. In other words, it's looking more and more (to me, anyway) as if this bug is a legitimate Djang