Re: super() argument 1 must be type, not None

2009/12/22 TiNo <tinodb@gmail.com>:
> /../ for some reason it throws the
> following error since a while (don't know since when, don't know what
> changed, can't find anything suspicious in hg log...) "super() argument 1
> must be type, not None". When I run with pdb.set_trace as the first line of
> the save method in the dev server, I can see that Lid is indeed None. What
> is surprising is that ALL my imports are None (User, datetime, models,
> etc.). I vaguely remember encountering this error before, but I don't
> remember what I did to fix it.

I have no idea how to fix it but I might have seen a similar problem;
Have you inspected globals()? What happened to me was that the
imported names existed in globals but they all pointed to None, hence,
useless. I could reimport something in the scope it were to be used,
but a function couldn't see other functions/symbols in the same
module!

HM

--

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@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.