Understand what it means that everything in Python is an object...

[bytecrunch]

Hello everyone,

I am new to the forum and relatively new to Python. I understand that Python considers everything as an "object". Lists, variables, functions, classes, methods are all considered to be objects.

However, I believe the use of the term "object" is different from the use of the term object used in OOP. Any programming language is independent of the programming paradigm it may use. But it seems that Python, by calling everything an object, is intrinsically connected to OOP even if I believe it is not the case since we can code in Python without doing OOP...

Is that correct? Could anyone clarify if there is any similarity, connection or lack of it between the usage of term "object" in Python and in OOP?

Thanks,
bytecrunch

[buran]

When we say everything is an object it has the same meaning as in OOP paradigm. Everything, e.g. built-i types or collections, has attributes - properties and methods. Even functions are objects. And you can subclass the built in types.

In more narrow sense object is the base class from which everything inherits in python

[bytecrunch]

Thank you,

So is it correct to say that Python is inherently an object oriented programming language?

[bytecrunch]

Thank you,

So is it correct to say that Python is inherently an object oriented programming language?

[Jeff900]

Thank you,

So is it correct to say that Python is inherently an object oriented programming language?

I think the problem is that Python is often used as a scripting language. But if fact, like buran mentioned, everything in python is an object. Even a simple variable like a string or integer is an object, which has its own attributes, methods etc.

So if you ask me, yes. Even if people use Python code 'just' as a scripts, they are in fact working with plenty of objects.

[bytecrunch]

Thanks Jeff900,

Sorry, I am a beginner. What do you mean exactly when you say "just" Python scripts? To me, a script is how we call a Python program.

And you said, everything is an object which seems to be one of the hallmarks of OOP. But coding in Python does not imply OOP.

[Jeff900]

Thanks Jeff900,

Sorry, I am a beginner. What do you mean exactly when you say "just" Python scripts? To me, a script is how we call a Python program.

And you said, everything is an object which seems to be one of the hallmarks of OOP. But coding in Python does not imply OOP.

With scripting I basically mean you will just run some code at once. To analyse data for example, or do something with a bunch of files etc. It has a specific beginning and an end, unlike programs that will be kept alive one way or another. But I realise this is my opinion and kind of subjective...

But to give an example for the fact that even in a simple 'script' you're using objects, take a look at the following code.

>>> number = 1
>>> type(number)

Output:
<class 'int'>

In this example you can see a simple integer is not just an integer. It is a class (object) which is used to define integers. You can create your own classes in Python to create your own specific objects. Creating your own classes may feel more like OOP, but in fact with using Python you're working with objects all the time.

[bytecrunch]

Thank you.

Some say that Python is not a "pure" object oriented language (I guess some language like smalltalk are) but I now believe it is not completely correct.

A module is also an object like anything else in Python. And the module's attributes are the functions and classes that the module contains, correct?

thanks again!

[nilamo]

Yes, that's correct.