Re: [sage-release] Sage 6.4.rc0 released

2014-11-03 Thread kcrisman
Jonathan, do you happen to know if Jmol is actually using Java 1.7 features? If not then it should be compiled with javac -target 1.6 or something like that to be compatible with older JREs. See http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html#crosscomp-options

Re: [sage-release] Sage 6.4.rc1 released

2014-11-03 Thread kcrisman
Does rc1 still have the issue reported at (among other places) http://trac.sagemath.org/ticket/16640#comment:43 in the command line? If so, that should be a blocker, as it is a pretty big change from 6.3 behavior, which I just confirmed still respects the viewer keyword. sage: sphere() # Jmol

Re: [sage-release] Sage 6.4.rc1 released

2014-11-03 Thread Volker Braun
On Monday, November 3, 2014 1:58:40 PM UTC, kcrisman wrote: sage: sphere(viewer='tachyon') # fine in 6.3, for some reason gives a Jmol in 6.4 rc0 How is that even consistent with the rest of the graphics framework? There is no plot(sin, viewer='svg'). However sphere().show(viewer='tachyon')

Re: [sage-release] Sage 6.4.rc1 released

2014-11-03 Thread Volker Braun
Also, what is the expected result of sage: sphere(viewer='tachyon').show(viewer='jmol') On Monday, November 3, 2014 2:18:56 PM UTC, Volker Braun wrote: On Monday, November 3, 2014 1:58:40 PM UTC, kcrisman wrote: sage: sphere(viewer='tachyon') # fine in 6.3, for some reason gives a Jmol in

Re: [sage-release] Sage 6.4.rc0 released

2014-11-03 Thread Gutow, Jonathan H
There used to be such an error message. I haven't got time until later today to look into this. It is possible that when we moved to using check calls directly from python that we lost the version checking that I had put in the scripts they replaced. Does anybody remember? Jonathan On Nov

Re: [sage-release] Sage 6.4.rc0 released

2014-11-03 Thread Volker Braun
On Sunday, November 2, 2014 5:10:19 AM UTC, Clemens Heuberger wrote: $ /local/sage/sage-6.3/sage -n directory='sage.sagenb' Traceback (most recent call last): ... File string, line 1 notebook(directory=rsage.sagenb) ^

Re: [sage-release] Sage 6.4.rc0 released

2014-11-03 Thread Clemens Heuberger
Am 2014-11-03 um 16:05 schrieb Volker Braun: IMHO that is the expected outcome for an optional command line argument. If you don't want the command line parsing to end (and not treat directory... as value) then you should use sage -n -- directory=sage.sagenb I'd appreciate if we would

Re: [sage-release] Sage 6.4.rc1 released

2014-11-03 Thread Volker Braun
On Monday, November 3, 2014 2:34:14 PM UTC, William Stein wrote: Personally I 'renderer' instead of 'viewer', since that's the terminology used, e.g., by THREE.js Another possibility would be display=svg, say. That could be generalized to something like latex(..., display='mathjax').

Re: [sage-release] Sage 6.4.rc0 released

2014-11-03 Thread Volker Braun
You can't really deprecate that yet make the notebook selectable, either -n takes an option or not. On the plus side the error that you'll get is pretty self-explanatory. $ ./sage -n foo=bar CRITICAL:root:unknown notebook: foo=bar Error, notebook must be one of default, ipython, sagenb but got