Python (and Python C API): __new__ versus __init__

by

The difference mainly arises with mutable vs immutable types.

__new__ accepts a type as the first argument, and (usually) returns a new instance of that type. Thus it is suitable for use with both mutable and immutable types.

__init__ accepts an instance as the first argument and modifies the attributes of that instance. This is inappropriate for an immutable type, as it would allow them to be modified after creation by calling obj.__init__(*args).

Compare the behaviour of tuple and list:

>>> x = (1, 2)
>>> x
(1, 2)
>>> x.__init__([3, 4])
>>> x # tuple.__init__ does nothing
(1, 2)
>>> y = [1, 2]
>>> y
[1, 2]
>>> y.__init__([3, 4])
>>> y # list.__init__ reinitialises the object
[3, 4]

As to why they’re separate (aside from simple historical reasons): __new__ methods require a bunch of boilerplate to get right (the initial object creation, and then remembering to return the object at the end). __init__ methods, by contrast, are dead simple, since you just set whatever attributes you need to set.

Aside from __init__ methods being easier to write, and the mutable vs immutable distinction noted above, the separation can also be exploited to make calling the parent class __init__ in subclasses optional by setting up any absolutely required instance invariants in __new__. This is generally a dubious practice though – it’s usually clearer to just call the parent class __init__ methods as necessary.

More Related Contents:

  1. Create an object using Python’s C API
  2. ImportError: dynamic module does not define init function (initfizzbuzz)
  3. Multithreading with Python and C api
  4. How to generate random binary numbers 0 or 1 with length of N and with option to control the probability of having 0 or 1?
  5. Approximating data with a multi segment cubic bezier curve and a distance as well as a curvature contraint
  6. Speed comparison with Project Euler: C vs Python vs Erlang vs Haskell
  7. It is more efficient to use if-return-return or if-else-return?
  8. How do you call Python code from C code?
  9. Py_initialize / Py_Finalize not working twice with numpy
  10. Extending setuptools extension to use CMake in setup.py?
  11. python tracing a segmentation fault
  12. How do I convert a Python list into a C array by using ctypes?
  13. Why is matrix multiplication faster with numpy than with ctypes in Python?
  14. How To catch python stdout in c++ code
  15. Run a python script with arguments
  16. Can we use C code in Python?
  17. How to pass a 2d array from Python to C?
  18. Python ? (conditional/ternary) operator for assignments [duplicate]
  19. Difference between np.int, np.int_, int, and np.int_t in cython?
  20. Using Cython To Link Python To A Shared Library
  21. Equivalent to GetTickCount() on Linux
  22. Calling Python script from C++ and using its output
  23. Wrapping a pre-initialized pointer in a cython class
  24. Building Mesa for windows 7. Mesa 9.1
  25. C++ conversion from NumPy array to Mat (OpenCV)
  26. Embedding Python in C, linking fails with undefined reference to `Py_Initialize’
  27. Writing code translator from Python to C? [closed]
  28. Installing lxml for Python 3.4 on Windows x 86 (32 bit) with Visual Studio C++ 2010 Express
  29. Extending python – to swig, not to swig or Cython
  30. Call python code from c via cython

Leave a Comment