title: Python deployment with virtualenv (on a no-internet-access server)
body: <p>My production server has no access to the internet, so it's a bit a mess copying all the dependencies from my dev machine to the production/development server.</p>
  
  <p>If I'd use virtualenv, I'd have all my dependencies in this environment. Doing this I'd also be able to deploy it on any machine, which has python &amp; virtualenv installed.</p>
  
  <p>But I've seen this rarely, and it seems kind of dirty.
  Am I wrong and this could be a good practice, or are there other ways to solve that nicely?</p>