• easy to start using
• free and open source
• (almost) portable
• high-level
• interpreted, not compiled
• well suited for REPL = Read Eval Print Loop

Another Example

Writing in Python is like writing pseudocode. Suppose you know, that

\[ e^x=\sum_{k=0}^\infty \frac{1}{k!}x^k = 1 + x + \frac{x^2}{2!} + \dots \]

Every object has:

• id — where it's located (~memory address)
• type — a set of values and operations on these values
• value — the actual value

• In general, 1 bit represents only two values (it's 0 or 1)
• 1 byte = 8 bits, and this already represents integers from 0 to 255 or from -127 to 127

Can it be depending on the platform:

• 4 bytes (32 bits) or
• 8 bytes (64 bits)?

Cpython open source realization:

									struct _longobject {
										// macros with
										// 1. the object’s reference counter (8 bytes)
										// 2. and a pointer to the corresponding type object (8 bytes)
										// 3. and extension field ob_size (8 bytes)
										PyObject_VAR_HEAD
										// int value adds 0, 4 (32x) or 8 bytes (64x)
										// SUM(for i=0 through abs(ob_size)-1) ob_digit[i] * 2**(SHIFT*i)
										digit ob_digit[1];
									};