Re: Django Test framework commits (r3658-r3661)

2006-08-30 Thread [EMAIL PROTECTED]
Malcolm, Hmm... ok I was running 3.1.3 on OSX (installed via darwinports). I've upgraded to 3.3.7. Also upgraded pysqlite to the latest in darwinports (2.0.5). But the tests fail for many_to_one and many_to_many whenever .count() is used with .distinct(). Specifically: (many_to_one:) Reporter.o

Re: Django Test framework commits (r3658-r3661)

2006-08-29 Thread Malcolm Tredinnick
On Mon, 2006-08-28 at 01:14 -0700, [EMAIL PROTECTED] wrote: > Hi Russ, > > Nice work! > > FYI I submitted a patch (#2490 [1] ) a while ago to get runtests.py to > produce an error if no DJANGO_SETTINGS_MODULE is in the env. Not sure > if this is something you want, but I've updated it to work p

Re: Django Test framework commits (r3658-r3661)

2006-08-28 Thread [EMAIL PROTECTED]
Hi Russ, Nice work! FYI I submitted a patch (#2490 [1] ) a while ago to get runtests.py to produce an error if no DJANGO_SETTINGS_MODULE is in the env. Not sure if this is something you want, but I've updated it to work post r3661 - it does make it a little bit easier to work out how to run the

Re: Django Test framework commits (r3658-r3661)

2006-08-27 Thread Russell Keith-Magee
Hi again, Following some concerns from Adrian, part of the testing patches have been rolled back (as of r3666). The testing framework itself will continue to work; however, the 'pseudo client' will be unable to inspect template specific details. Apologies for any inconvenience. Yours, Russ Mag

Django Test framework commits (r3658-r3661)

2006-08-27 Thread Russell Keith-Magee
Hi all,Revisions 3658-3661 are the commits of the first two phases of the Django Testing Framework. These changes should have no impact on any existing project. However, should you wish to unit test your Django application, there is now a framework (controlled by ./manage.py test) that will allow y