f Hardy
> Sent: Wednesday, May 06, 2009 4:37 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Assertion failure in IPy 2.6 while running
> Django
>
> On Sun, May 3, 2009 at 3:59 PM, Dino Viehland
> wrote:
> > Do you happen to know what baseName is when the
On Sun, May 3, 2009 at 3:59 PM, Dino Viehland wrote:
> Do you happen to know what baseName is when the assertion is hit?
>
Hit this again (different subclass of Field); baseName was Default20.
This might have something to do with the fact that Field.__init__ has
20(!) optional, defaulted paramet
f Of Jeff Hardy
> Sent: Sunday, May 03, 2009 1:19 PM
> To: Discussion of IronPython
> Subject: [IronPython] Assertion failure in IPy 2.6 while running Django
>
> The assertion is on line 91 of PythonFunction.Generated.cs (as of
> r49699, anyway): mi != null. Why mi is null I have no
] Assertion failure in IPy 2.6 while running Django
The assertion is on line 91 of PythonFunction.Generated.cs (as of
r49699, anyway): mi != null. Why mi is null I have no idea.
The smallest repro I've found still requires Django (any recent
checkout should do):
>>> from django.db import mode
The assertion is on line 91 of PythonFunction.Generated.cs (as of
r49699, anyway): mi != null. Why mi is null I have no idea.
The smallest repro I've found still requires Django (any recent
checkout should do):
>>> from django.db import models
>>> message = models.TextField('message')
If I had t
