[sage-release] Sage 7.0 virtual appliance

2016-01-26 Thread Volker Braun
The Sage 7.0 virtual appliance can now be found at http://files.sagemath.org/win/index.html Starting with this version, the Jupyter notebook is the default. Not only is it a modern user interface, it also gives you easy access to a shell inside the VM without cryptic key combinations. --

[sage-release] Sage 7.0 virtual appliance

2016-01-26 Thread Johan S . R . Nielsen
Awesome timing! Monday morning I'll begin teaching a course, and I was a bit depressed about the Windows-users having to use an old Sage and running the notebook... Best, Johan Volker Braun writes: > The Sage 7.0 virtual appliance can now be found at > http://files.sagemath.org/win/index.html

Re: [sage-release] Re: Sage 7.0 released

2016-01-26 Thread Dima Pasechnik
On Tuesday, 26 January 2016 17:23:48 UTC, kcrisman wrote: > > Untested is broken: > http://ask.sagemath.org/question/32330/sage-notebook-is-not-working/ > This is via the .app bundle, I think. What could have changed to make > this not work? > is it notebook-specfic, or a not working OSX

Re: [sage-release] Re: Sage 7.0 released

2016-01-26 Thread kcrisman
> Untested is broken: >> http://ask.sagemath.org/question/32330/sage-notebook-is-not-working/ >> This is via the .app bundle, I think. What could have changed to make >> this not work? >> > > is it notebook-specfic, or a not working OSX binary? > It seems to be that the notebook doesn't

[sage-release] Re: Sage 7.0 released

2016-01-26 Thread Volker Braun
I've deleted the Sage-7.0 OSX binaries On Tuesday, January 19, 2016 at 9:21:53 AM UTC-5, Volker Braun wrote: > > The "master" git branch has been updated to Sage-7.0. As always, you can > get the latest beta version from the "develop" git branch. Alternatively, > the self-contained source

Re: [sage-release] Re: Sage 7.0 virtual appliance

2016-01-26 Thread Volker Braun
On Tuesday, January 26, 2016 at 7:41:28 PM UTC-5, kcrisman wrote: > > One thing I should have asked on that ticket is whether it's possible to >> test it without any impact on .sage/sage_notebook.sagenb, and then to kill >> the new ipynb files to test again in a different configuration or