Irrational Exuberance

You are writing a comment about Development to Deployment in Django, here is a quick summary:

An overview of my pipeline between development and deployment for Django projects. Fabric and Git turn a potentially unhappy task into something very quick and easy.

You are responding to this comment written by Will Larson on November 5th 2008, 09:06.

I have two situations I deal with:

1. One project per machine.
2. Multiple projects, all of which I develop, on one machine.

For both those scenarios I am comfortable with either a) not upgrading anything or b) upgrading everything. If I wasn't, then I do agree that using separate python environments for each project would be a good idea.

As for interlibrary dependencies, that just isn't something that crops up very often for me, and when it does I handle it manually. If it was a consistent problem (like if I was running a webhost), then I'd probably resort to separate Python environments.

Please be aware that comment forms go stale after one hour.

@@ ruby
def a (b, c):
  b * c
end
@@

 ### This is an h3 title
#### This is an h4 title
**this is bold**
*this is italics*

1. This is an
2. ordered list

* And an unordered
* list too

[this is a link](http://www.lethain.com/ "Lethain")