Closed bucweat closed 10 years ago
Investigating this is on my todo list for "very soon" because I'd like to sort this out and make it available to everyone myself. There's definitely no harm in giving it a shot, though I don't know right off what (if anything) may go wrong. Just trying would provide good initial data points, though, and we could use this ticket as a support request placeholder for me to help make this upgrade happen.
Roger copy I will give it a try. I'm sort of new to the whole Vagrant/Chef thing so reading up on that now and will give it a shot. Beauty of VMs is if you dork it up you toss and start over...
I think all you should have to do to try it out is update the version for IPython in the mtsw_requirements.txt file to ipython==2.0
On May 30, 2014, at 9:31 AM, bucweat notifications@github.com wrote:
Roger copy I will give it a try. I'm sort of new to the whole Vagrant/Chef thing so reading up on that now and will give it a shot. Beauty of VMs is if you dork it up you toss and start over...
— Reply to this email directly or view it on GitHub.
I was having trouble getting vagrant to install newer versions after I updated mtsw2e-requirements.txt. But I did finally get it to take I think with vagrant reload --provision. I had to run "ipython notebook" from vagrant ssh terminal to figure out there is a tornado dependency that requires a newer version. So the changes to mtsw2e-requirements.txt are:
tornado==3.1.0
ipython==2.1.0
The listing of notebooks is a bit different as it includes directory listing of ipynb folder. But it looks like everything works...
Thanks, this is really encouraging and makes the plunge to roll this out just a bit less daunting since you've confirmed that it seems to be pretty painless. I really appreciate your help, and I'll work hard to get this (and a few other loose ends) wrapped up soon and rolled out to everyone.
Can I just update the mtsw2e-requirements.txt to point to IPython 2.0 or even 2.1?