On Tuesday, November 5, 2019 at 7:33:07 AM UTC-5, Eric Gourgoulhon wrote:
>
> 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
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:
https://wiki.gentoo.org/wiki/Project:Quali
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. https://groups.google.com/d/msg/sage-devel/DmB
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, shoul
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 fail
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 r
On 11/3/19 4:55 PM, VulK wrote:
On the same note: the current implementation of `is_jvm_available` is not
really robust and I should open a ticket about this; any suggestion for a
better implementation?
S.
const false
Does it do anything except jmol? The right way to do it would be to add
-
All test passed!
Gentoo linux running on x86_64 Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz
Three doctests in src/sage/rings/padics/padic_lattice_element.py failed on
safe -t --all but were succesful when the file was checked individually.
I confirm my green light
S.
* Dima Pasechnik [2019-
I figured out that the error I posted depended on an ambient variable that I
have set um in my rc files, namely
export _JAVA_OPTIONS="-Dawt.useSystemAAFontSettings=on -Dswing.aatext=true"
with this `java -version` returns
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatex
Thanks!
Next up an error while building docs
[dochtml] [discrete_] from
/opt/sage-python3/src/doc/en/reference/discrete_geometry/sage/geometry/triangulation/point_configuration.rst:
[dochtml] [discrete_] Traceback (most recent call last):
[dochtml] [discrete_] File
"/opt/sage-python3/local/
On Sun, 3 Nov 2019, 16:57 VulK, wrote:
> I have issues with a symlink when installing ipython:
>
> """
> ...
> Successfully installed ipython-5.8.0
> Cleaning up...
> Removed build tracker '/tmp/pip-req-tracker-x6b62y1w'
>
> real0m3.382s
> user0m3.027s
> sys 0m0.498s
>
I have issues with a symlink when installing ipython:
"""
...
Successfully installed ipython-5.8.0
Cleaning up...
Removed build tracker '/tmp/pip-req-tracker-x6b62y1w'
real0m3.382s
user0m3.027s
sys 0m0.498s
Copying package files from temporary location
/opt/sage-python3/loca
Building now
S.
* Frédéric Chapoton [2019-11-03 05:18:13]:
Could please some of the many plus-one-ing people try the branch at #28660
and report there if it works for them, namely builds a working python3-sage
by default ?
Frédéric
Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a
Could please some of the many plus-one-ing people try the branch at #28660
and report there if it works for them, namely builds a working python3-sage
by default ?
Frédéric
Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit :
>
> Maybe I missed it, but I didn't find a ticket for t
Please feel free to edit and enhance the wiki page about the switch :
https://wiki.sagemath.org/Python3-Switch
Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit :
>
> Maybe I missed it, but I didn't find a ticket for that. I think now would
> be a good time to flip the switch, tho
+1
On Sunday, October 27, 2019 at 9:58:23 AM UTC+10, Volker Braun wrote:
>
> Maybe I missed it, but I didn't find a ticket for that. I think now would
> be a good time to flip the switch, though. Any thoughts?
>
--
You received this message because you are subscribed to the Google Groups
"sage
+1 for Dima's remark. Has anybody used the old Sage notebook with a Python
3-based Sage ?
Le dimanche 27 octobre 2019 16:52:34 UTC+1, Dima Pasechnik a écrit :
>
> +1, although it seems that #25837 (making sagenb optional) should happen
> first.
>
> On Sun, Oct 27, 2019 at 4:52 PM mmarco >
> w
+1, although it seems that #25837 (making sagenb optional) should happen first.
On Sun, Oct 27, 2019 at 4:52 PM mmarco wrote:
>
> If all the issues ar solved... sure. I was even surprised that we started
> haviong betas of version 9 with python 2 (I assumed that the witch to version
> 9 would
If all the issues ar solved... sure. I was even surprised that we started
haviong betas of version 9 with python 2 (I assumed that the witch to
version 9 would be mostly about the transition to python 3).
+1
El domingo, 27 de octubre de 2019, 1:58:23 (UTC+2), Volker Braun escribió:
>
> Maybe I
+1
Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit :
>
> Maybe I missed it, but I didn't find a ticket for that. I think now would
> be a good time to flip the switch, though. Any thoughts?
>
--
You received this message because you are subscribed to the Google Groups
"sage-de
Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a écrit :
>
> Maybe I missed it, but I didn't find a ticket for that. I think now would
> be a good time to flip the switch, though. Any thoughts?
>
+1
Eric.
--
You received this message because you are subscribed to the Google Groups
21 matches
Mail list logo
