title: Controlling Python package versions
body: <p>So I am staring down a situation and I am hoping you good people might have some suggestions about how to address it with minimal complexity.</p>
  
  <p>I am maintaining a small lab that does its development in Python.  All of our users are internal but maintain their own machines.  Our own source files are kept in SVN, but our various dependencies are stored on a lab wiki for download.   For the first time in many years we are looking at updating our dependency versions and I would like to find something a bit cleaner then 'copy installer or egg from website, store on lab ftp, tell users to get it from there'.</p>
  
  <p>Our internal users tend to be non-technical, which is why the old setup was just a bunch of installers sitting around.  This has its own problems though, it is a pain to maintain (esp in terms of minor updates), you have to grab separate installers for each OS, and not all packages have nice .exe installers ready to go so users have to install some packages one way and other packages another way.  Not a problem for developers but it is not great for users.</p>
  
  <p>For things like RPMs, in the past, I have been able to throw together a local repo and provide users with something they install once and then all their updates go through the repo we controlled.  This has worked great in terms of users not getting annoyed by complexity and developers having strict control over which versions of various libs they have installed.</p>
  
  <p>I looked around and saw questions that kinda touched on this, but nothing that quite addressed this type of problem.  Are there any quick and dirty ways to do something like this?</p>
  
  <p>Thanks!</p>