Hi Christian,
On Mon, Dec 6, 2010 at 10:38 AM, Christian Stump
wrote:
> I gonna open a ticket on this, if no one was already looking at it.
The problem is fixed at ticket #8395 [1]. For example, after applying
the patches on that ticket, this is what I get using the sample
session you posted abo
Hi,
I would like to know if it could be considered to add a feature that
would allow one to disable spell-checking inside a worksheet. I often
find my code all underlined in red, and need to disable spell-checking
for every code block that I create (it's on by default).
What I suggest is a new fe
Salut,
somehow, graphs don't like multiple edges very much:
sage: D = Graph()
sage: D.allow_multiple_edges(True)
sage: D.add_edges([(0,1),(0,1)])
sage: D.edges()
[(0, 1, None), (0, 1, None)]
sage: D.degree()
[2, 2]
sage: D.delete_edge(0,1)
sage: D.edges()
[(0, 1, None)]
sage: D.degree()
[2, 2]
On 2010-12-05 23:17, John H Palmieri wrote:
> On Dec 5, 2:00 pm, Jeroen Demeyer wrote:
>> On 2010-12-05 18:37, John H Palmieri wrote:
>>
>>> What's the difference? Right now we never call pipestatus with
>>> arguments in this form, do we?
>>
>> Actually we do in the "make build" rule:
>> $(PI
On Dec 5, 2:00 pm, Jeroen Demeyer wrote:
> On 2010-12-05 18:37, John H Palmieri wrote:
>
> > What's the difference? Right now we never call pipestatus with
> > arguments in this form, do we?
>
> Actually we do in the "make build" rule:
> $(PIPE) "cd spkg && ./install all 2>&1" "tee -a ../inst
On 2010-12-05 18:37, John H Palmieri wrote:
> What's the difference? Right now we never call pipestatus with
> arguments in this form, do we?
Actually we do in the "make build" rule:
$(PIPE) "cd spkg && ./install all 2>&1" "tee -a ../install.log"
So the question becomes: do we want to write
On Sun, Dec 5, 2010 at 10:52 AM, Iftikhar Burhanuddin
wrote:
> This is on mod.math.washington.edu.
>
> burha...@mod:~$ uname -m
> x86_64
>
> E = 2^(10^10)
>
> works fine on the subsequent attempts. I wonder why the error on the first
> attempt.
Perhaps there wasn't enough free RAM available on
mo
This is on mod.math.washington.edu.
burha...@mod:~$ uname -m
x86_64
E = 2^(10^10)
works fine on the subsequent attempts. I wonder why the error on the first
attempt.
On Sun, 5 Dec 2010, John Cremona wrote:
On a 64-bit machine I can compute 2^)10^10) with no trouble.
On a 32-bit machine I
On Dec 5, 6:15 pm, Iftikhar Burhanuddin
wrote:
> Please explain the reason for the error. Is the number too big? If so what
> is the range of integer computability?
>
> Regards,
> Ifti
>
> sage: E = 2^(10^10)
The error explains,
RuntimeError: exponent must be at most 2147483647
that is 2**31-1
On a 64-bit machine I can compute 2^)10^10) with no trouble.
On a 32-bit machine I get a more explicit error message than you reported:
RuntimeError: exponent must be at most 2147483647
which answers your question. Note that this number is 2^31-1, and
that 10^10 is larger than that by a factor
On Dec 5, 2:16 am, Jeroen Demeyer wrote:
> The command spkg/pipestatus runs two commands in a pipeline CMD1 | CMD2
> and returns the exit status of CMD1 if CMD1 fails but CMD2 is successful
> (normally, CMD1 | CMD2 would always exit with the status of CMD2). This
> is useful in Makefile where CMD
Please explain the reason for the error. Is the number too big? If so what
is the range of integer computability?
Regards,
Ifti
sage: E = 2^(10^10)
---
RuntimeError Traceback (most recent call l
It seems that sage -f sagenb-VERSION doesn't actually do anything. It
does NOT change the devel/sagenb-main directory. This issue also breaks
upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
actually upgraded. Either I'm doing something wrong, or I'm making the
sagenb spkg w
The command spkg/pipestatus runs two commands in a pipeline CMD1 | CMD2
and returns the exit status of CMD1 if CMD1 fails but CMD2 is successful
(normally, CMD1 | CMD2 would always exit with the status of CMD2). This
is useful in Makefile where CMD2 is a "tee" command.
In #10339, there is some di
14 matches
Mail list logo
