Author(s):	Trey Hunner
Location	Reis River Ranch
Date	apr Sun 27	Days Raw Files
Start	15:15	First Raw Start	error-in-template
Duration	00:25:00	Offset	None
End	15:40	Last Raw End
Chapters
Total cuts_time	None min.

https://pretalx.northbaypython.org/nbpy-2025/talk/XVXLJ3
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Variables_and_objects_its_pointers_all_the_way_down.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	In Python, assignment statements don't copy objects, and data structures don't actually contain objects. These two surprising facts have a *lot* of interesting consequences and are the reason behind many of Python's design decisions. In this talk, we'll explore the reference-like nature of Python's variables and objects, noting both the benefits and gotchas involved. Among other ideas, we'll see that in Python: - The word "change" is ambiguous - Copying is usually explicit - Infinitely recursive data structures aren't a concern - And tuples aren't always immutable During the process, we'll poke at our own mental model of Python and we'll get a bit pedantic at times. Join us to learn how in Python, it's pointers (or references, names, bindings, or aliases) all the way down. markdown
Comment:	production notes