Regardless of how "useful" or awesome the Jupyter notebook is and how many
people in scientific computing are using it, there is a substantial
ecosystem now designed around the Sage notebook proper - including perhaps
even the not-yet-one-year-old "Sage for Undergraduates" book? - and a lot
of
Hi,
On Tue, Dec 29, 2015 at 10:22:28AM -0800, mmarco wrote:
> In #19781 there are some issues with several optional packages that don't
> build or work correctly on 32 bits.
Most of the time, the problems with 32-bit architectures come from
incomplete doctests that are only tested on 64-bit arch
> On 31/12/2015, at 09:31, Volker Braun wrote:
>
> There isn't an easy way to "delete everything thats not needed in a
> system-wide install". Ideally you should only need the "sage" script and the
> SAGE_LOCAL tree, but that is currently not the case.
>
> In the binary packaging I'm excludin
There isn't an easy way to "delete everything thats not needed in a
system-wide install". Ideally you should only need the "sage" script and
the SAGE_LOCAL tree, but that is currently not the case.
In the binary packaging I'm excluding the following:
- exclude: '**.pyc'
- exclude: '
> On 31/12/2015, at 04:07, William Stein wrote:
>
> why is there
> both build and src/build?
Unfortunate naming perhaps. src/build is created by python when building
sage itself. Not much you can do about that name. It is tempting to just
nuke it but if you build with debug it will contain cyt
Dear all,
Who is running the patchbot named Hera-Optiplex ? This patchbot is not
registered in the page
http://wiki.sagemath.org/buildbot/owners
This patchbot currently misbehaves. Its owner is kindly asked to stop it
or restart it and check that it works.
Frederic
--
You received this mes
Hi,
I just built Sage-6.10 from source and installed quite a few packages,
which uses a total of 10G
of precious disk space:
salvus@compute0-us:/projects/sage/sage-6.10$ du -sch * |sort -h
0 config.log
0 data
4.0Kbootstrap
4.0Khome
4.0KVERSION.txt
8.0KMakefile
8.0K
