veyepar: Ship your Python code faster with PEX

Author(s):	Shalabh Chaturvedi
Location	Reis River Ranch
Date	jul Sat 29	Days Raw Files
Start	14:40	First Raw Start	14:22
Duration	00:25:00	Offset	0:17:19
End	15:05	Last Raw End	15:18
Chapters	00:00 0:11:42
Total cuts_time	30 min.

https://pretalx.northbaypython.org/nbpy-2023/talk/RGRCLN
raw-playlist raw-mp4-playlist encoded-files-playlist host archive mp4 svg png

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

State:
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:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	A lot of Python code is shipped around in Docker images. But did you know there is another way to ship Python code to production that is... better in some situations? This talk covers our exploration into making code deployment faster for our users (our product runs user code in our cloud). We will cover the limits we faced with Docker builds and container provisioning, various options we explored, and why we settled on PEX. [PEX](https://pex.readthedocs.io) is a tool that packages Python code and dependencies into a single file. It provides various features such as determinism (given the same input files, you get a bit-for-bit identical output file), isolation (a PEX file runs in the bundled environment, isolated from the system’s site-packages), composition (multiple PEX files can be combined to form new environments), and more. We used a number of these feature to great effect in our solution. By using PEX in addition to Docker we were able to reduce the time a developer waits for code to deploy from 3-4 minutes to about 30 seconds. Shipping code isn't the only use for PEX. Once we see how PEX files work, we will also go over a few fun tips and tricks that are handy for everyday Python development. markdown
Comment:	production notes

2023-07-29/14_22_41.ts Apply: 14:40:58 - 14:52:40 ( 00:11:42 ) S: 14:22:41 - E: 14:52:40 D: 00:29:59 (Start: 1097) show more... >>> 18*60 + 17 1097 >>> 18*60 + 21 1101

vlc ~/Videos/veyepar/nbpy/nbpy23/dv/barn/2023-07-29/14_22_41.ts :start-time=01097.0 --audio-desync=0

	Raw File	Cut List
	14:22:41		seconds: 1097.0 Wall: 14:40:58
Duration	00:29:59
	14:52:40		seconds: 0.0 Wall: 14:22:41
Comments:		>>> 1860 + 17 1097 >>> 1860 + 21 1101
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this