On Sat, Jun 27, 2009 at 1:22 AM, Kevin Kubasik wrote:
> So, up until now, most of the work on windmill hasn't exactly been 'tester
> ready' in that, if you didn't you my exact incantation of settings, luck,
> module versions and love, you didn't get very far. While I still haven't
> gotten real d
So, up until now, most of the work on windmill hasn't exactly been 'tester
ready' in that, if you didn't you my exact incantation of settings, luck,
module versions and love, you didn't get very far. While I still haven't
gotten real docs done (my original plan for the week) I have learned a
valuab
Not too much to report this week, except I have the HttpResponse
charset handling (ticket 10190) working and passing all the test
suites. I changed test_client_regress for this to work, because it was
expecting strange behavior. I have no doubt there is some tweaking to
be done to the code, and I
On Fri, Jun 26, 2009 at 2:17 PM, Nathan Auch [Sybase] wrote:
>
> I'm working on getting the SQL Anywhere backend to pass the test suite
> for the current Django development branch. I've run into a number of
> tests that are failing intermittently due to the order in which results
> are returned. F
I'm working on getting the SQL Anywhere backend to pass the test suite
for the current Django development branch. I've run into a number of
tests that are failing intermittently due to the order in which results
are returned. For example, the regressiontests/null_fk test sometimes
fails with:
