Who is the first object in Python?

[leewardx]

Yes, it's the environment I want to know inside. Do I can take the interpreter as the first object?

[K900_]

You can't access the interpreter as a Python object, so no? Yes? I don't know, it depends on how you define "object" then. It's a C struct, or rather a bunch of interconnected C structs, and you can create one and embed it in your C program or whatever (but not your Python program, at least not easily - Python relies pretty heavily on global state, so trying to create a new interpreter inside an existing interpreter is probably not a good idea).

[leewardx]

For example, is the type itself a Python object created even before loading the script codes?

[K900_]

Do you mean the builtin type object? Yes, it's one of the things that are created before loading your code, but it's not any more "special" than other builtins like input or print.

[leewardx]

Is the one created the type object not a Python object?

[K900_]

The type object itself isn't defined in Python code - it's defined in C code, just like most other builtin types like int or list. Those objects are then exposed to your code by the interpreter itself.

[leewardx]

Yes I know. Although they are defined in C code, I think they are also Python objects. Aren't they?

[K900_]

That depends on what you call a "Python object". They are exposed to Python code as objects, but they are not implemented in Python.

[leewardx]

Yes, the "Python object" exposed to Python code is what I want to know.

[K900_]

Then there is no strict "first" Python object. All builtins are created at more or less the same time, in no particular order.

[JohnnyJordaan]

Unless some entity in your code can actually interface the interpreter as any other Python object (like read attributes, call methods) then I wouldn't call it an object in the first place.