Author(s):	Cory Benfield
Location	Track 1
Date	sep Sun 06	Days Raw Files
Start	10:40	First Raw Start	error-in-template
Duration	00:30:00	Offset	None
End	11:10	Last Raw End
Chapters
Total cuts_time	None min.

https://kiwi.pycon.org/schedule/presentation/91/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf You_Dont_Care_About_Efficiency_Synchronous_Code_Is_Dying.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:	If you write blocking code, you don’t care about efficiency. There, I said it. It’s 2015, and still the vast majority of Python programmers write essentially synchronous code that blocks on network I/O. This approach, while simple to reason about, struggles mightily with scaling up and out into software that does a lot of network I/O. Worse, it makes it difficult to write code that reacts rapidly to changing conditions. The writing is on the wall for this kind of software, as the community shifts towards writing software that embraces asynchronicity. In this talk we’ll discuss why synchronous software is a problem, what your options are to move away from it, and what challenges are being faced by the Python ecosystem as we try to move towards a brave new asynchronous world. markdown
Comment:	production notes