QA/Execution/Web Testing/Automation/Virtual Environments: Difference between revisions

QA/Execution/Web Testing/Automation/Virtual Environments (view source)

238 bytes added , 6 November 2015

no edit summary

Confirmed users

2,177

edits

Revision as of 17:18, 2 March 2015 (view source) Davehunt (talk \| contribs) No edit summary ← Older edit		Latest revision as of 14:32, 6 November 2015 (view source) Davehunt (talk \| contribs) No edit summary
Line 1:		Line 1:
	Virtual environments are isolated Python environments. They allow freedom to install specific versions of dependencies without affecting the global site-packages. They also make it easy to throw away a broken environment and start again. We recommend using '''virtualenvwrapper''' for managing your virtual environments. See the documentation for [http://virtualenvwrapper.readthedocs.org/en/latest/install.html] and a [http://virtualenvwrapper.readthedocs.org/en/latest/command_ref.html command reference].		Virtual environments are isolated Python environments. They allow freedom to install specific versions of dependencies without affecting the global site-packages. They also make it easy to throw away a broken environment and start again. We recommend using '''virtualenvwrapper''' for managing your virtual environments. See the documentation for a guide to [http://virtualenvwrapper.readthedocs.org/en/latest/install.html installation] and the [http://virtualenvwrapper.readthedocs.org/en/latest/command_ref.html command reference]. There's also a useful introduction to virtualenv and virtualenvwrapper in [http://www.silverwareconsulting.com/index.cfm/2012/7/24/Getting-Started-with-virtualenv-and-virtualenvwrapper-in-Python this blog post].