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 Alexander Artemenko on November 5th 2008, 08:03.

I have two question about you deployment process.

First, how do you deal with iterlibrary dependencies? For example, if appA does not works with appB < 0.1.2, or appA broke when appB > 1.0.0 is installed?

Second, how do you upgrade complex libraries or frameworks like django? If you install all applications and libraries into the common site-packages, than it would be difficult to upgrade all projects to the latest django, for example, if there are any backward incompartibilities. Don't you think, that it would be better to create separate python environment for each project?

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")