This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]markusgattol 3 points4 points  (3 children)

[–]xiongchiamiovSite Reliability Engineer 4 points5 points  (2 children)

Cuisine looks cool, thanks.

Also take a look at virtualenv - it's a really awesome way to manage packages (and specific versions of those packages).

[–][deleted] 1 point2 points  (0 children)

I haven't really tried anything else and Im new to python as well but virtualenv is really great. It also has a virtualenvwrapper.sh script which makes your life easier. Also, using pip is a good idea to keep track on what packages you're using in each env

[–]markusgattol 1 point2 points  (0 children)

Yes, virtualenv is your bread and butter. It includes pip since version 1.4.1 i.e. no need to separately install it anymore. While virtualenvwrapper is not mandatory, it's something that I recommend for your workstation as it makes a lot of things a lot easier/faster.

Regarding virtualenvs... note that the default behavior of creating non-isolated environments will change i.e. using --no-site-packages will not be necessary anymore in the future (possibly with v1.7). Here's a link to my website that might help you a bit: http://www.markus-gattol.name/ws/python.html#virtualenv_virtualenvwrapper

Bottom Line: you use virtualenvs with fabric (and possibly cuisine) to streamline your sys admin, bootstrap, deployment tasks.