Hi
On 8 January 2015 at 07:27, Ivan Andrus wrote:
> On Jan 7, 2015, at 9:04 PM, kcrisman wrote:
>
> On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
>>
>> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
>> started sage successfully for the first time
> On Jan 7, 2015, at 9:04 PM, kcrisman wrote:
>
> On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
> started sage successfully for the first time but I have trouble running sage
> after that. It consta
Fixes to the source files?
On Tuesday, January 6, 2015 3:23:10 AM UTC-5, Volker Braun wrote:
>
> I built a new binary. Harald, can you replace the F21 binary with the new
> one on the mirrors?
>
> buildbot@build:~$ md5sum
> binaries/sage-6.4.1-x86_64-Linux-Fedora_21_x86_64.tar.gz
> cbdf8a8a1e4ee
On Wednesday, January 7, 2015 7:57:36 PM UTC-5, Ruizhi Deng wrote:
>
> I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
> started sage successfully for the first time but I have trouble running
> sage after that. It constantly shows that Sage server failed to start.
> A
I'm a new comer to Sage and I'm running sage on my mac with OS X 10.10. I
started sage successfully for the first time but I have trouble running
sage after that. It constantly shows that Sage server failed to start.
And here's the log information I find. It might be useful.
Setting environment
On Tue, 06 Jan 2015 at 12:39PM -0800, William Stein wrote:
> Who is also going to the Joint Mathematics Meetings in San Antonio?
I'll be there.
Dan
--
--- Dan Drake
- www.math.wisc.edu/~ddrake/
---
--
You received this message because you are subscribed to the Google Groups
"sage-s
On Wed, Jan 7, 2015 at 8:34 AM, kcrisman wrote:
>
>> Only 2 years later, and I found a way around segmentation faults due to
>> memory problems. It seems that my looping functions fill up memory over time
>> and lead to segmentation faults at random stages. I now define such
>> functions using the
> Only 2 years later, and I found a way around segmentation faults due to
> memory problems. It seems that my looping functions fill up memory over
> time and lead to segmentation faults at random stages. I now define such
> functions using the @fork decorator and then they don't seem to cause
Only 2 years later, and I found a way around segmentation faults due to
memory problems. It seems that my looping functions fill up memory over
time and lead to segmentation faults at random stages. I now define such
functions using the @fork decorator and then they don't seem to cause
crashes
How did you download/compile/run Sage?
--
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 ema
On 2015-01-07 00:32, Wai Yan Pong wrote:
Hello,
I'm unable to have Sage 6.4.1 running. My ipython2 seems running
fine. Attached is the Crash Report.
It seems that you're trying to run Sage with your system Python/IPython
installation. This isn't really supported.
How did you download/c
Sándor Czirbusz
--
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@goog
12 matches
Mail list logo
