Everything is an object in python - object class and type class

Chris Angelico rosuav at gmail.com
Mon Jun 1 20:32:51 EDT 2015


On Tue, Jun 2, 2015 at 10:24 AM, TheDoctor <dreamingforward at gmail.com> wrote:
> On Monday, June 1, 2015 at 7:03:49 AM UTC-5, Eddilbert Macharia wrote:
>> I think i kind of understand now.
>>
>> Instead of python having data types like int, string, e.t.c it has two primitive types which are class type and class object which are created by python interpreter during its setup .using this two classes python is able to create some more data types
>
> Eddibert, don't let this crowd (Terry, Stephen, et al.) confuse you.  They are as confused about it as you are.
>
> The truth is, that they've told a lie to themselves (everything is an object) to hide some details FROM THEMSELVES in their model.  They climb a ladder of ambiguity anytime there's a new problem in their model and call it a "type", or they pull out the "metaclass" term (because no one really knows that that is, so they feel *pretty* safe).
>
> A type is not an object in the same way an instantiated type is an object -- anymore than a blueprint for a building is the building itself.

And don't let dreamingforward confuse you, because he is flat-out
wrong. An integer is an object, because you can manipulate it as one.
A function is an object. A dictionary is an object. And a type is an
object too. There is no significant difference here.

ChrisA



More information about the Python-list mailing list