ance of 'type' representing
> >>> that class is created by calling type.__init__. What really gets me is
> >>> how can 'type' be an instance of itself. In order to create 'type' we
> >>> would need to call type.__init__, but it seem
at when a class
type(ob) simply looks up ob.__class__. For built-in classes, that is
all it means.
declaration is found in the code, an instance of 'type' representing
that class is created by calling type.__init__. What really gets me is
how can 'type' be an instance of i
an that when a class
> > declaration is found in the code, an instance of 'type' representing
> > that class is created by calling type.__init__. What really gets me is
> > how can 'type' be an instance of itself. In order to create 'type' we
&g
an that when a class
> > declaration is found in the code, an instance of 'type' representing
> > that class is created by calling type.__init__. What really gets me is
> > how can 'type' be an instance of itself. In order to create 'type' we
&g
ance of 'type' representing
> that class is created by calling type.__init__. What really gets me is
> how can 'type' be an instance of itself. In order to create 'type' we
> would need to call type.__init__, but it seems at this point it
> wouldn't e
ass is created by calling type.__init__. What really gets me is
how can 'type' be an instance of itself. In order to create 'type' we
would need to call type.__init__, but it seems at this point it
wouldn't exist. Probably a dumb question, which I hope someone can
explain