veyepar: Reliable Testing & Deployments with pip and Wheels

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:	I plan to briefly introduce pip requirements files and the wheel format. I will then demonstrate an approach for structuring requirements files, using "snapshot" requirement files, and building "wheelhouses" that get committed to your VCS. This approach has the following benefits: - known working & tested dependencies are clearly communicated between developers - project setup for new developers is simplified - build servers no longer throw erroneous errors if PyPI is down - production environments no longer need build tools installed on them - production environments are guaranteed to be running on the same version of dependencies that were developed on and tested markdown
Comment:	production notes

2014-10-05/14_28_46.dv Apply: 14:28:46 - 14:53:56 ( 00:25:10 ) S: 14:28:46 - E: 14:53:56 D: 00:25:10 show more...

vlc ~/Videos/veyepar/pytexas/pytexas2014/dv/MSC_2300_B/2014-10-05/14_28_46.dv :start-time=00.0 --audio-desync=0

2014-10-05/14_53_56.dv Apply: 14:53:56 - 14:59:49 ( 00:05:53 ) S: 14:53:56 - E: 14:59:49 D: 00:05:53 show more...

vlc ~/Videos/veyepar/pytexas/pytexas2014/dv/MSC_2300_B/2014-10-05/14_53_56.dv :start-time=00.0 --audio-desync=0

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