Nothingness and identity in Python and Django
summary
Explains concrete surprises and fixes: Python distinguishes identity and equality so is vs == behaves oddly because of small-integer caching (integers >256 aren’t interned), Django needs distinct representations for nothing — None vs null vs blank — and the work of modeling real people forces choices about nullable name parts, form handling, filtering and ordering. Gives a real case: a Django person model for Cardiff University School of Medicine and cites Pan African PyCon attendance at 323 people.
AI-written summary · about
chapters (7)
- 0:00Start
- 11:05PHILOSOPHICAL CONCEPTS AND PROGRAMMING
- 12:00FAMILIAR TERRITORY
- 18:21REPRESENTING THE WORLD
- 23:35SIMPLE AND SUCCESSFUL
- 25:38PYTHON'S INTERNAL METAPHYSICS OF BEING
- 34:47PROGRAMMERS AND PHILOSOPHY
related talks
01h 18mPython 103: Mmmm... Understanding Python's Memory Model, Mutability, and Methods
30mThe Wizardry of Metaprogramming
01h 06mEffective Django
01h 07mWhat Does It All Really Mean
31mLife Under the A Guide to Python's Internal Conventions
24m"Normalize until it hurts; denormalize until it works" in Django
46mOn Being Pythonic
36mThe Afterlife: Languages after JavaScript