On Dec 8, 11:39 pm, Ian Clelland <clell...@gmail.com> 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 be useful to have for comparison purposes is the test results when run on 2.x with an unmodified Django (from the mirror at https://bitbucket.org/django/django/), so that people can see what the potential performance penalty is for calling u() and b() all over the place. I realise that it's not going to be a scientific comparison, but it will probably show up if there is appreciable overhead (I haven't found that to be the case, but it might vary based on platforms and backends). I posted these from the tests (for the sqlite backend) run on my Ubuntu VM, in response to a question from Armin Ronacher: Django on 2.x unported: 4482 tests in 368.972s, skipped = 90 Django on 2.x, with u(), b(), sys.exc_info() etc: 4478 tests in 367.635s, skipped = 90 Django on 3.x, with u(), b(), sys.exc_info() etc: 4423 tests in 372.946s, skipped = 96 It would be interesting to see if a similar pattern emerges on OSX. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
