The lack of boolean type coercion is more serious than it looks like at
first glance.
(starting from the example at http://code.djangoproject.com/ticket/7190)
In [1]: import django.newforms as forms
In [2]: from django.newforms.models import model_to_dict
In [3]: from simple.models import Simple
Your patch works, thanks. Perhaps you could add it to
http://code.djangoproject.com/ticket/7190; I tried the patch there, but
it doesn't work in this case.
Mike
Pim Van Heuven wrote:
> Hi Michael,
>
> Can you apply this patch and run the tests again?
> I have been running Django with this pa
Hi Michael,
Can you apply this patch and run the tests again?
I have been running Django with this patch for a long time but never
got around to submitting it.
Pim.
Michael Glassford wrote:
> I'm still trying to run the Django unit tests for the first time. I've
> worked through most of the e
On Thu, Jun 19, 2008 at 9:57 AM, Michael Glassford <[EMAIL PROTECTED]>
wrote:
>
> I'm still trying to run the Django unit tests for the first time. I've
> worked through most of the errors--all of them so far proved to be
> caused by the MySQL/InnoDB ordering problem when deserializing objects
> t
I'm still trying to run the Django unit tests for the first time. I've
worked through most of the errors--all of them so far proved to be
caused by the MySQL/InnoDB ordering problem when deserializing objects
that I asked about in another thread. However, I have one more set of
errors that app
