Re: Strange Model behavior

2009-01-26 Thread Mark Jones
I guess I was just too tired when I wrote it, I just forgot the * and ** on the 2 arguments. I have some initialization that I'm doing in __init__ but had removed that to make the example shorter and was still seeing the problem. Thanks for the help, those 3 *'s fixed the whole problem On Jan

Re: Strange Model behavior

2009-01-26 Thread Steve Holden
Dj Gilcrease wrote: > What do you need to do in __init__ > You don't actually need to fo anything at all! As you have the code now you're calling the superclass's __init__ with two arguments: the newly created instance, a tuple of the other positional args (if any) and a dict of the keyword argum

Re: Strange Model behavior

2009-01-25 Thread Dj Gilcrease
What do you need to do in __init__ Dj Gilcrease OpenRPG Developer ~~http://www.openrpg.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@goo

Re: Strange Model behavior

2009-01-25 Thread Martin Conte Mac Donell
On 1/26/09, Mark Jones wrote: > class Fails(models.Model): > code = models.CharField(max_length=64) > quizid = models.IntegerField(null=False, blank=False) > published_on = models.DateTimeField(auto_now_add=True) > > def __init__(self, *args, **kwargs): > super(Fails, sel