Question

in c/c++, you have variables in stack when you create a local variable inside a function.

http://effbot.org/zone/call-by-object.htm

CLU objects exist independently of procedure activations. Space
for objects is allocated from a dynamic storage area /…/ In
theory, all objects continue to exist forever. In practice, the
space used by an object may be reclaimed when the object isno
longer accessible to any CLU program.

Does this mean objects in python is created from heap(as in malloc in c/c++)? and the objects are deallocated when there ‘s no name associated with them?(like smart pointers)?

Example:

def foo(a): 
  result = []
  result.append(a)
  return result

foo("hello")

myList = foo("bye")

So the first result([]) was created in the heap and got deallocated because there’s no name associated with it?

Answer 1

Yes, all Python objects live on the heap (at least on CPython.) They are reference-counted: they are de-allocated when the last reference to the object disappear. (CPython also has a garbage collector to break cycles.)

In CPython your first list disappears as soon as the function returns since you did not bind the return value to a name and the reference count dropped to zero. In other implementation the object may live longer until the garbage-collector kicks in.

Some objects (like open files) have resources attached that are automatically freed when the object is deallocated, but because of the above it is not recommended to rely on this. Resources should be closed explicitly when you are done with them.