> On Friday, December 16, 2016 at 1:41:59 AM UTC, Sho Takemori wrote:
>>
>> Thank you for the information. But I sill don't understand why this error
>> occurs.
>>
>> I build Sage in the Docker container using the Sage repo as follows.
>>
>> git chec
Thank you for the information. But I sill don't understand why this error
occurs.
I build Sage in the Docker container using the Sage repo as follows.
git checkout a83e25136481efb99d9cb8c00dde3065c0d04894
make
Then I got the following error message
(if I use the commit f26b322f76034b8122603cbc4
p would be appreciated.
Sho Takemori
--
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 e
Thank you very much for your explanation. I have seen your post at
sage-devel before, but completely forgot it.
I guess it would be better to raise an error or print a message than to
return a wrong result, if it is a known bug and not fixed yet.
Sho Takemori
2016年11月22日火曜日 19時27分58秒 UTC+9
and Sage is running on Ubuntu 16.04.
Best regards,
Sho Takemori
--
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.co
val('4')
s.quit()
Sho Takemori
2016年2月19日金曜日 11時52分04秒 UTC+9 Daniel Lännström:
>
> I have noticed that when using the sage0 interface zombie processes remain
> even after running the sage.interfaces.quit.expect_quitall function.
>
> Is this a bug? Is there some way to
replace start_cleaner like this
<https://gist.github.com/stakemori/067e254dc3d2054cf151>, zombie processes
are not spawned.
By the way, I do not understand why calling this function in gp.eval or
gap.eval is necessary, since child processes (such as gp, gap) are killed
when Sage exits.
Sho T
