On Monday, June 1, 2015 at 7:33:11 PM UTC-5, Chris Angelico wrote: > On Tue, Jun 2, 2015 at 10:24 AM, TheDoctor <dreamingforw...@gmail.com> wrote: > > 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.
An integer in Python *acts* like an object, in some narrow sense can indeed be said to BE one. But no one uses them like that in practice (purity was trying to beat practicality in the case of ints) -- they use them like ints, with the extra super-nice shortcuts of having them arbitrarily-sized. And that was available before the type-class unification. > A function is an object. A dictionary is an object. Yep. > And a type is an > object too. OOPs. Mark -- https://mail.python.org/mailman/listinfo/python-list
