Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-12 Thread Tom Evans
On Fri, Dec 9, 2011 at 7:43 PM, Joe & Anne Tennies wrote: > The thing is, we aren't trying to "scientifically correct" statistics. What > we're aiming to say is, "This is not so wildly different as to be of any > concern." We aren't looking for minor difference, but orders of magnitude > differenc

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-09 Thread Ian Clelland
On Fri, Dec 9, 2011 at 11:43 AM, Joe & Anne Tennies wrote: > The thing is, we aren't trying to "scientifically correct" statistics. > What we're aiming to say is, "This is not so wildly different as to be of > any concern." We aren't looking for minor difference, but orders of > magnitude differen

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-09 Thread Joe & Anne Tennies
The thing is, we aren't trying to "scientifically correct" statistics. What we're aiming to say is, "This is not so wildly different as to be of any concern." We aren't looking for minor difference, but orders of magnitude difference. If you are that worried about a <2% difference in speed, you pr

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-09 Thread Ian Clelland
On Fri, Dec 9, 2011 at 8:36 AM, Tom Evans wrote: > On Fri, Dec 9, 2011 at 4:17 PM, Ian Clelland wrote: > > Unscientifically, trunk without the Python 3 patches runs 1.5% faster w/ > > SQLite, 0.6% faster w/ MySQL. (based on a sample size of 1 :) ) > > > > I know you put the word 'unscientificall

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-09 Thread Vinay Sajip
On Dec 9, 4:36 pm, Tom Evans wrote: > I know you put the word 'unscientifically' in there, but you can draw > no conclusions from doing one run of each like that. See my reply > earlier in the week on how to simply and easily do valid statistical > testing. > > http://osdir.com/ml/django-develop

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-09 Thread Tom Evans
On Fri, Dec 9, 2011 at 4:17 PM, Ian Clelland wrote: > Unscientifically, trunk without the Python 3 patches runs 1.5% faster w/ > SQLite, 0.6% faster w/ MySQL. (based on a sample size of 1 :) ) > I know you put the word 'unscientifically' in there, but you can draw no conclusions from doing one ru

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-09 Thread Ian Clelland
On Thu, Dec 8, 2011 at 5:56 PM, Vinay Sajip wrote: > > On Dec 8, 11:39 pm, Ian Clelland wrote: > > I now have Django passing its entire unit test suite with the MySQL and > > SQLite backends, on Python 2.6.7 and Python 3.2.2 > > Ian, > > Thanks for the comprehensive summary and eliminating those

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-08 Thread Vinay Sajip
On Dec 8, 11:39 pm, Ian Clelland wrote: > I now have Django passing its entire unit test suite with the MySQL and > SQLite backends, on Python 2.6.7 and Python 3.2.2 Ian, Thanks for the comprehensive summary and eliminating those last few issues on the MySQL backend. One more thing which might

Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

2011-12-08 Thread Ian Clelland
I now have Django passing its entire unit test suite with the MySQL and SQLite backends, on Python 2.6.7 and Python 3.2.2 Details: Common environment: OS X 10.6.8 MacPorts 2.0.3 MySQL 5.1.60 from MacPorts SQLite 3.7.9 from MacPorts Django from https://bitbucket.org/vinay.sajip/django/ hash 6b1413