this is now #22933, ready for review.
Note that it's not a complete fix;
sage: vars()
still fails
sage: v=vars()
sage: for k in v.keys(): print v[k]
works with the ticket branch.
On Tuesday, May 2, 2017 at 9:01:42 PM UTC+1, Dima Pasechnik wrote:
>
> In fact, complete_sandpile has been remo
In fact, complete_sandpile has been removed, but the lazy import for it is
still there.
So this has to be fixed. I will open a ticket.
On Tuesday, May 2, 2017 at 8:48:47 PM UTC+1, Dima Pasechnik wrote:
>
> no, it's more serious, perhaps something to do with lazy imports?
>
> sage: v=vars()
> sag
no, it's more serious, perhaps something to do with lazy imports?
sage: v=vars()
sage: v['complete_sandpile']
) failed:
AttributeError: 'module' object has no attribute 'complete_sandpile'>
(I found the value of the guilty key by running
sage: for k in v.keys(): v[k]==None;
until it breaks)
(sa
I think it's a (pretty?) printing problem. For me, running
sage: a = vars()
works without error, but then
sage: a
gives the error. Same thing happens with locals().
--
John
On Tuesday, May 2, 2017 at 2:37:25 AM UTC-7, Dima Pasechnik wrote:
>
> Indeed, it appears that vars() is broken
The relevant line is
ImportError: libgfortran.so.3: cannot open shared object file: No such
file or directory
You need to install libgfortran. For this, run this command in a terminal:
sudo apt-get install libgfortran
--
You received this message because you are subscribed to the Goog
I have ubuntu on an internal ssd for a long time. I even didn't make a
swap partition as suggested and ubuntu is very speedy so sage is too
Le 02/05/2017 à 11:21, Dima Pasechnik a écrit :
On Monday, May 1, 2017 at 9:55:16 PM UTC+1, Jim Mooney wrote:
On Monday, April 24, 2017 at 3:07:0
Indeed, it appears that vars() is broken, and has been broken since Sage
7.5, at least.
Running
sage: vars()
ends with
---
TypeError Traceback (most recent call last)
in ()
> 1 vvv
/hom
On Monday, May 1, 2017 at 9:55:16 PM UTC+1, Jim Mooney wrote:
>
>
>
> On Monday, April 24, 2017 at 3:07:00 AM UTC-7, Dima Pasechnik wrote:
>>
>>
>> another option is to install a 2nd hard drive/SSD, (almost trivial on
>> desktop) and install Linux there.
>> The cost of such disks, 100GB would g
No. I didn't. I just saw the log file again and found that
it complains about libgfortran. I installed libgfortan-5-dev from
the ubuntu repository. It works fine now. But I thought sage comes
with complete gcc. It may be necessary to add that libgfortran is required
in the
installation instructi
On 02/05/2017 00:20, Jim Mooney wrote:
On Monday, April 24, 2017 at 2:57:41 AM UTC-7, vdelecroix wrote:
Dear Jim,
For windows status, have a look at [1]. Concerning data storage with
flash drive, the live USB key [2] gives you access to your hard drive.
So I don't understand your limitation
On window (7 and 10) when I run sagenb (sage:notebook()) then graphique
and calculation work. For example sqrt(16) i got 4, if I run the
jupyter-notebook icon it runs, then I input the same sqrt(16) and then
it seems frozen ? No answer... The star shows up but never stops... I
read somewhere t
Hi
On 2 May 2017 at 09:57, Venkataraman S wrote:
> Sage crashes in Ubuntu 17.04. I have attached the
> crash report. The problem seems to be with Ipython.
> * SageMath version 7.6, Release Date: 2017-03-25 *
> Best,
>
Do you have libgfortran3 installed?
Regards,
Jan
--
.~.
/V\
Sage crashes in Ubuntu 17.04. I have attached the
crash report. The problem seems to be with Ipython.
* SageMath version 7.6, Release Date: 2017-03-25 *
Best,
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group an
--
S. Venkataraman
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@
14 matches
Mail list logo
