Author(s):	Brett Cannon
Location	Colony Ballroom
Date	aug Sat 10	Days Raw Files
Start	16:30	First Raw Start	error-in-template
Duration	00:20:00	Offset	None
End	16:50	Last Raw End
Chapters
Total cuts_time	None min.

https://2013.pycon.ca/en/schedule/presentation/96/
raw-playlist raw-mp4-playlist encoded-files-playlist host public mp4 svg png

assets release.pdf From_Source_to_Code_How_CPythons_Compiler_Works.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:	How the heck does CPython take a blob of bytes you call source code and create another blob of bytes called bytecode which it is able to execute to make the magic of Python programs work? This talk's aim is to provide a conceptual answer to that question. The overall process of tokenizing, parsing, creating an AST, and then finally emitting bytecode will be covered. If you have no clue what any of those previous words meant, don't worry! This talk will be accessible to people who are not compiler experts. We'll also cover how various parts of the compiler are exposed through Python's standard library so you can play with what you learn afterwards. markdown
Comment:	production notes