| Project: | pip | ||||
pip freeze files and similar techniques like buildout have been used for reliable testing and reliable deployments for some time. But they are not flexible enough to deal with situations like OpenStack where there are dozens of separate codebases, evolving independently, which still need the same rigour and reliability.
Enter pip constraints, new in 7.1.0. I will cover their use, design, and how we're using them in devstack (and thus OpenStack CI) - and how you can (and should) use them in your local projects.
Robert Collins is a Distinguished Technologist on the continuous integration / continuous deployment team in HP Cloud Services. For the last 4 years he has been walking the fine line between development and operations. He is also a developer on the Debian project, and has contributed to many other projects, including (but certainly not limited to): bazaar, Launchpad, Ubuntu, subunit, testresources, testtools, testscenarios, testrepository, fixtures, zope fixtures, config manager, cygwin and squid.
Robert has been involved with open source development and Python for a number of years, with a "tremendous passion for high quality, well tested software". He has been described as a "Champion of test driven development", and a "meticulous software developer".
He lives in Rangiora, New Zealand with his wife & young daughter.
