You Have to Find the Source | Inside Python Part 1
Sign up for DUTC Weekly: https://mailchi.mp/dutc/ytweekly
LinkedIn: / do-n-t-use-this-code
Website: https://www.dontusethiscode.com/index...
Upcoming events: learning.dutc.io
Looking for training? Contact [email protected]
In this series, our goal is to learn how to learn about all of the topics covered in our main sessions. We will show you how to take a deep dive into the Python interpreter to answer these types of questions for yourself!
This series is part of (More) Python Basics for Experts - Bonus session. In this series, we will look to answer the following questions:
What is an abstract syntax tree? What is the ast module? When might I want to write a NodeVisitor or similar?
What actually runs when I run a Python function? What is the dis module? What is bytecode? How do I disassemble a Python function? What does this tell us?
What debugging mechanisms are provided by the sys module? What is sys.settrace and how can it be useful in real projects?
How do I build CPython from source? How do I build it with debugging symbols? How do I debug CPython using gdb from the C-level (and where could this be useful)?
What are the core parts of the CPython interpreter? What is located where? - - How do they all fit together? What is ceval.c and can I learn from looking at the main interpreter loop?
What is a PyObject and a PyObject*? What is a tp_ method? How do the builtin types actually work? What is abstract.c and object.c?