We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Object Internals

Formale Metadaten

Titel
Object Internals
Untertitel
Memory address in Python
Serientitel
Anzahl der Teile
130
Autor
Lizenz
CC-Namensnennung - keine kommerzielle Nutzung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
This talk is intended to explain to participants what is happening under the hood when they are playing around with different python built-in data structures. Explain the concepts such that they are not surprised by the behavior of Python. Pre-requisites: Anyone who knows built-in python data structures like List, Dictionaries, set, etc. Curiosity questions that the talk answers: 1. What happens to the memory address when * operator is used? 2. When does python create a new object in memory? 3. What does it refer to the mutability and immutability of objects in Python? 4. If the outer object is immutable but the reference objects are mutable. Can the elements be added? 5. What is the difference at the memory level when we refer to deep copy and shallow copy in lists? 6. Operations like List.sort and sorted in python? What to use, when to use? What happens at the memory level? 7. What is the difference between is vs ==? When should it be used? 8. Lots and lots of interesting examples. 9. How do we determine the memory reference id associated with the object? 10. Meaning of assigning a value to a variable in Python. The existing slides use screenshots. But, I'll be including more interesting examples and would replace the screenshots with GIFs. So, that folks get a feeling of live coding and remain interested in the presentation. Along with the visual representation of what is happening at the memory level.