|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || Typical errors when dealing with mutable objects and not having a full understanding of how certain Python internals work Alternative talk title
|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || Immutable objects have read-‐‑only value 1st key concept
|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || Names (attrs.) are pointers and = copies the reference 2nd key concept
|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || Python code is interpreted at import time 4th key concept
|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || Python code is interpreted at import time Interpreted means executed 4th key concept
|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || Python code is interpreted at import time Interpreted means executed This includes objects creation 4th and 5th key concepts
|| MUTABLE VS. IMMUTABLE OBJECTS || PYCON ES 2015 || PABLO ENFEDAQUE VIDAL || @pablitoev56 || > Shallow copy uses the reference to the object > Assignment, constructor by copy, arguments in function calls > Be aware of it! > Class attributes remain in the class > Create instance mutable attributes in __init__ > Functions default values remain in the function > Create mutable default values inside the function to sum up