Well, I've got it running on my desktop now and I have the following conclusions:
1) Python is icky and pip is not a patch on Ruby's Bundler
2) Class2go is not quite ready for prime time - the admin side of things is somewhat rough round the edges (NB just admin - not the tutor interface). I'm sure it's fine if you're Stanford, but if you are another institution trying to set it up you hit a few niggles (e.g. course.stanford.edu
hard coded in places!)
3) The installation documentation ends a bit abruptly. It's a bit like when your satnav says "You have reached your destination" but you are in the middle of open countryside and you are left wondering what to do and where to turn next!
4) HOWEVER, given time, I can see Class2go being the best choice to host your own MOOCs. It just depends on what Stanfords motivations are - whether they want to be the platform vendor of choice or whether they simply want it to work for them.