On Friday, March 31, 2017 at 7:08:25 AM UTC-4, kcrisman wrote:
>
>
>
>
> Try again!
>>
>
> Will do once I am connected to power source ;-)
>
Nearly finished but because I (accidentally, but usefully) built binaries
of 8.beta0 due to the default target being "develop" not "master" I have
the us
Matplotlib version is 1.5.1. You can look in
SAGE_ROOT/local/var/lib/sage/installed to see a file for each Sage package,
including a version number. Also, as Justin points out, you can look at
SAGE_ROOT/build/pkgs, and in particular
SAGE_ROOT/build/pkgs/matplotlib/package-version.txt.
Python v
On Apr 1, 2017, at 08:02 , Henri Girard wrote:
> Hi,
> I wonder if sage-8.0 is using matplotlib 2.0, because the color I get are
> looking like it ?
> How can I know which matplotlib I use and which python I use (2 or 3) ?
The content of $SAGE_ROOT/build/pkgs sometimes contains information that
Hi,
I wonder if sage-8.0 is using matplotlib 2.0, because the color I get
are looking like it ?
How can I know which matplotlib I use and which python I use (2 or 3) ?
Regards
Henri
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscrib
I would like in particular feedback on the "Take me to the new
Sage/Jupyter notebook" button in ExportSageNB.
When clicking that button, do you get
(A) a directory listing of the current directory
(B) a login screen where you are asked for a token
You should get (A) but under certain unknown c
On Friday, March 31, 2017 at 3:44:02 AM UTC+2, kcrisman wrote:
>
> Remember, we want LOTS OF TESTING of this one - including the Mac
> interface. Any possible bugs in the move to the ExportSageNB interface
> must be exposed.
>
I haven't checked it with ExportSageNB, but it's probably worth a