I apologize for late reply and being inactive. I will transfer these elisp
repos to sagemath github organization (and add license to ob-sagemath). To
transfer them, I think first I have transfer them to an account who has owner
or admin permission of sagemath github organization. It would be
Le mercredi 6 novembre 2019 04:51:31 UTC+1, Sho Takemori a écrit :
>
> I apologize for late reply and being inactive. I will transfer these elisp
> repos to sagemath github organization (and add license to ob-sagemath).
Thank you very much, Sho !
> To transfer them, I think first I have
On 2019-11-05, E. Madison Bray wrote:
> The generated file `build/make/Makefile` is output by the
> `./configure` script. In fact, that's its main purpose. When
> switching branches in this case the best thing to do is to re-run
> `./configure`.
Concerning the original question how to
On Tue, Nov 5, 2019 at 9:51 AM Thierry wrote:
>
> Hi,
>
>
> On Mon, Nov 04, 2019 at 01:00:17PM +, Dima Pasechnik wrote:
> > How does one switch off multiprocessing in docbuild?
> > (it's ludicrous not being able to build docs on a VM with 2GB of memory)
>
> Not an answer but a workaround: to
Hi,
On Mon, Nov 04, 2019 at 01:00:17PM +, Dima Pasechnik wrote:
> How does one switch off multiprocessing in docbuild?
> (it's ludicrous not being able to build docs on a VM with 2GB of memory)
Not an answer but a workaround: to build Sage doc for SDL on
pentium3-emulated VM, i do:
I am not sure I agree with setting this at build time: a jvm could be
installed afterwards and/or updated independently of sage
S.
* Michael Orlitzky
[2019-11-04 08:49:18]:
On 11/3/19 4:55 PM, VulK wrote:
On the same note: the current implementation of `is_jvm_available` is not
really
On Mon, Nov 4, 2019 at 12:51 PM Dima Pasechnik wrote:
> configure:12690: g++ -E -std=gnu++11
> -I/Volumes/Transcend/wooster/computer-algebra/anaconda3/include
> conftest.cpp
>
> anaconda conflict?
>
I deleted it, used brew to install a few more packages, and
added some symlinks (which brew
I am saying that I am not super fond of the idea or recompiling because of a
java update: I can see how one could get confused. Either way, considering
that no-one noticed this "feature" till now I doubt that this will have any
impact.
On a side note: is jmol going to be replaced? If so,
On Tue, Nov 5, 2019 at 10:19 AM VulK wrote:
>
> I am not sure I agree with setting this at build time: a jvm could be
> installed afterwards and/or updated independently of sage
if the configuration of the system has changed,
one may have to re-configure/rebuild.
Or are you saying that Sage
On Fri, Sep 27, 2019 at 8:01 PM John H Palmieri wrote:
>
> I have been testing new versions of Simon King's p-group cohomology package.
> The current version doesn't work with Python 3, and he has been working
> (#28414) to fix this. My workflow:
>
> check out his git branch
> run ./sage -f
Le mardi 5 novembre 2019 11:34:55 UTC+1, Salvatore Stella a écrit :
>
> On a side note: is jmol going to be replaced? If so, should we just ignore
> the issue?
>
>
Jmol has been replaced by three.js as Sage's default 3d viewer in Sage
9.0.beta0,
cf.
On 11/5/19 5:18 AM, VulK wrote:
> I am not sure I agree with setting this at build time: a jvm could be
> installed afterwards and/or updated independently of sage
> S.
>
This is generally considered a bad practice because it leads to
unpredictability:
12 matches
Mail list logo
