Dear all,
at
http://groups.google.com/group/sage-support/browse_thread/thread/534306c87e7fac7a
I was asking about the apparently changed behaviour of "sage -t".
Georg suggested to move the discussion to sage-devel, so, here it
is...
On 20 Jun., 22:10, gsw wrote:
> On 20 Jun., 08:15, Simon King
William Stein wrote:
> What about control-enter? Can you make it so
> control-enter = linebreak
> shift-enter = submit
> ?
Control-enter is bound to spliteval_cell. To make control-shift-enter,
say, insert a line break, try augmenting notebook.py's tinyMCE.init()'s
setup with some code ri
On Fri, Jun 19, 2009 at 12:00:19PM -0700, Tom Boothby wrote:
> I'm the release manager for sage-4.0.3.
> Python to 2.6, and if I succeed, I'll rename the release to sage-4.1.
> In about an hour, I'm going to send out review requests.
Tom: thanks very much for your time on this!
To all (potential
2009/6/20 Craig Citro :
>
>>> Interesting ... that means that the call to sys.exit(0) is generating
>>> an exception that's getting caught in the except: clause. Can you file
>>> a ticket for this? I'll happily review it. :)
>>
>> I created a ticket #6364, without a patch though since it's outside
>> Interesting ... that means that the call to sys.exit(0) is generating
>> an exception that's getting caught in the except: clause. Can you file
>> a ticket for this? I'll happily review it. :)
>
> I created a ticket #6364, without a patch though since it's outside
> SAGE_ROOT/devel.
>
Actually
A nomination for this prize (and similar ones) would be a huge boost
for sage. I hope we don't forget to ask for you support! ;)
Harald
-- Forwarded message --
From: Frank Sottile
Date: Sat, Jun 20, 2009 at 18:49
PS: (share the following with your team:
http://www.sigsam.org
Hi,
It seems that there is a major bug in new symbolics simplify()
method involving "D" and symbolic function (Sage-4.0.1).
---
sage: f(x) = function('f',x)
sage: f(-x).diff(x)
-D[0](f)(-x)
sage: f(-x).diff(x).simplify()
-D[0](f)(x)
---
Notice that simplify() causes f(-x) to beco
ersion 4.4.0 20090526 prerelease that fixes other problem with build
>> I had with sage 4.0). Anyway - had to patch libsingular (it use
>> deprecated strchr form in 2 places, simple cast is enough to fix it
>> just as recommended on official porting guide for gcc 4.4) - there is
>&
Dear David,
On Fri, Jun 19, 2009 at 12:29:47PM +0200, William Stein wrote:
> On Fri, Jun 19, 2009 at 11:58 AM, wrote:
> > Hi William,
> >
> > I'd be happy to have a look at referee this.
Thanks so much for looking at this!
> > Do I need to apply the dozen or so patches, or what is requ
2009/6/20 Craig Citro :
>
>> That did the trick -- ran fine and no "failure" line at the end. (I
>> moved that line to the end as suggested)
>>
>
> Interesting ... that means that the call to sys.exit(0) is generating
> an exception that's getting caught in the except: clause. Can you file
> a ti
Hi,
I am wondering whether there is any policy/framework
for hooking-up a specialized integration code as a part
of integration algorithm in new symbolic?
I have been writing code for integration involving Dirac delta
generalized function to include the same in Sage.
The form of integrand that
William Stein wrote:
> On Sat, Jun 20, 2009 at 2:09 PM, Pat LeSmithe wrote:
>> Are there objections to displaying something like
>>
>> Sign into the Sage Notebook v4.0.2
>>
>> in place of
>>
>> Sign into the Sage Notebook
>>
>> on the notebook log-in page? It often helps to know which version is
On Sat, Jun 20, 2009 at 2:09 PM, Pat LeSmithe wrote:
>
>
> Are there objections to displaying something like
>
> Sign into the Sage Notebook v4.0.2
>
> in place of
>
> Sign into the Sage Notebook
>
> on the notebook log-in page? It often helps to know which version is
> running on sagenb.org or a
Are there objections to displaying something like
Sign into the Sage Notebook v4.0.2
in place of
Sign into the Sage Notebook
on the notebook log-in page? It often helps to know which version is
running on sagenb.org or alpha.sagenb.org, before logging in.
The actual change would be to use,
Before building gcc 4.4.0 on 't2' I needed to build mpfr, as it is
perquisite for gcc.
I built the latest version of mpfr (2.4.1) using the Sun supplied gcc
3.4.2 in /usr/sfw/bin. mpfr built and passed all 148 tests.
With the aid:
1) The aid of a patch to atlas
http://trac.sagemath.org/sage_
William Stein wrote:
> On Fri, Jun 19, 2009 at 9:21 PM, Dr. David
>> How can the bug be closed.
>
> I've closed it. Only a few people have the option to close tickets right now.
>
> William
Thank you. That's one less Solaris bug to worry over. Plenty more though
to occupy our time.
dave
--~
On Fri, Jun 19, 2009 at 9:21 PM, Dr. David
Kirkby wrote:
>
> Dr. David Kirkby wrote:
>> In the process of building Sage on t2, I noticed another failure, which
>> I'm somewhat surprised has not been seen on all platforms. I've
>> submitted this as ticket 6278, where more information is provided th
Hi,
I just tried the following.
1. Take a clean Sage-4.0.2 tarball and edit SAGE_ROOT/spkg/install
replacing the line
time make -f standard/deps $1
by
time make -j20 -f standard/deps $1
2. make. This builds a whole bunch of different spkg's in parallel.
At one point spkg/install
gets overwr
recommended on official porting guide for gcc 4.4) - there is
> patch against singular spkg from 4.0.2 -
> http://giniu.ravenlord.ws/singular-3-1-0-2-20090620.diff - and spkg
> itself - http://giniu.ravenlord.ws/singular-3-1-0-2-20090620.spkg -
> wasn't doing any patches for Sage
Compiled fine on OSX.4 G4 PPC.
There were a lot of warnings in Sphinx at the very end about duplicate
references within the English tutorial, usually with bibliography.rst.
- kcrisman
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups
20 matches
Mail list logo
