On Sun, Apr 5, 2009 at 1:13 AM, Carl Witty wrote:
>
> On Sun, Apr 5, 2009 at 12:33 AM, jeffblakeslee wrote:
>>
>> Here's how I got it. Ctrl-c after a couple seconds on the first one,
>> and then try the next.
>> --
>> | SAGE Ve
On Sun, Apr 5, 2009 at 12:48 PM, William Stein wrote:
> On Sun, Apr 5, 2009 at 1:13 AM, Carl Witty wrote:
>>
>> On Sun, Apr 5, 2009 at 12:33 AM, jeffblakeslee wrote:
>>>
>>> Here's how I got it. Ctrl-c after a couple seconds on the first one,
>>> and then try the next.
>>>
On Sun, Apr 5, 2009 at 1:13 AM, Carl Witty wrote:
>
> On Sun, Apr 5, 2009 at 12:33 AM, jeffblakeslee wrote:
>>
>> Here's how I got it. Ctrl-c after a couple seconds on the first one,
>> and then try the next.
>> --
>> | SAGE Ve
On Sun, Apr 5, 2009 at 12:33 AM, jeffblakeslee wrote:
>
> Here's how I got it. Ctrl-c after a couple seconds on the first one,
> and then try the next.
> --
> | SAGE Version 3.0.6, Release Date: 2008-07-30
Here's how I got it. Ctrl-c after a couple seconds on the first one,
and then try the next.
--
| SAGE Version 3.0.6, Release Date: 2008-07-30 |
| Type notebook() for the GUI, and license() for information.
On Sat, Apr 4, 2009 at 11:55 AM, jeffblakeslee wrote:
>
> Hello, This looks like a bug. It seems that after 3316 bits of
> precision
> the approximation of pi just puts out 0's. This doesn't seem to
> occur with the approximation of e.
>
> pi.n(3330)
> 3.1415926535897932384626433832795028841971
On Apr 4, 2009, at 11:55 AM, jeffblakeslee wrote:
> Hello, This looks like a bug. It seems that after 3316 bits of
> precision
> the approximation of pi just puts out 0's. This doesn't seem to
> occur with the approximation of e.
>
> pi.n(3330)
> 3.1415926535897932384626433832795028841971693993
