Hi,
David Harvey raised a speed question on
http://sagetrac.org/sage_trac/ticket/628
It's a legitimate concern, but as far as I can tell, it's a completely
orthogonal issue to that specific patch thanks to Pablo's clever coding (all
of the exceptional code only occurs if we aren't on the
Thank you for your comments on my patch
It is a legitimate concern, I agree (and could affect many
number-theoretical or similar functions); and the principle of
solution that you are proposing could be a good one. (I like the idea
of writing some code in cython that calls pari directly, I don't
Pablo mentioned that it'd be nice to have a Mercurial plugin for Trac.
It turns out (a bit unsurprisingly -- there seems to be a plugin for
everything for Trac) that there is an experimental one:
http://trac.edgewall.org/wiki/TracMercurial
I think it'd be a nice feature to have on the Trac
On Monday 10 September 2007 18:21, Pablo De Napoli wrote:
I could not read your modification to my patch since you've uploaded
that as an hg bundle. I think that for trac the best would be to
upload patches in plain text. That way, trac knows how to format it so
that it can be easy read on the
On Sep 10, 2007, at 4:44 PM, Joel B. Mohler wrote:
Hi,
David Harvey raised a speed question on
http://sagetrac.org/sage_trac/ticket/628
It's a legitimate concern, but as far as I can tell, it's a completely
orthogonal issue to that specific patch thanks to Pablo's clever
coding (all
On Sep 10, 3:30 pm, Mike Hansen [EMAIL PROTECTED] wrote:
Pablo mentioned that it'd be nice to have a Mercurial plugin for Trac.
It turns out (a bit unsurprisingly -- there seems to be a plugin for
everything for Trac) that there is an experimental
On Mon, September 10, 2007 1:44 pm, Joel B. Mohler wrote:
The principle refinement needed is: How can call_fast_integer_function
bewritten generically?
This does not address how one does this, and I'm not even sure this is
what you mean by generic, but:
Python includes a method decorator
On 9/10/07, David Harvey [EMAIL PROTECTED] wrote:
I'm not too comfortable with this suggestion... it's too specific to
integer arguments.
When someone calls e.g. binomial(x, y), is it possible to make that
call go directly to cython? We can't avoid the initial binomial
name lookup, that's
On Monday 10 September 2007 18:15, David Harvey wrote:
The binomial function then gets a prefix something like:
try:
call_fast_integer_function( x, m, _binomial_raw )
except CoercionError:
# compute binomial slowly
The principle refinement needed is: How can
cat /etc/issue gives:
Welcome to SUSE LINUX Enterprise Server 9 (x86_64) - Kernel \r (\l).
The tail end of the polymake build, when it crashes, has the
following:
make[2]: Leaving directory `/home/bc1/hamptonm/sage-2.8.3.6/spkg/build/
polymake-2.2.p2/build/modules/graph'
g++
William Stein [EMAIL PROTECTED] writes:
I've released sage-2.8.4.1, which is a very minor bugfix release:
Builds fine on Mac OS X 10.4.10, Intel Core 2 Duo:
real77m24.900s
user48m46.842s
sys 24m24.761s
...
SAGE build/upgrade complete!
All tests run by make test pass.
But sage -t
On Sep 10, 8:36 pm, Hamptonio [EMAIL PROTECTED] wrote:
cat /etc/issue gives:
Hello Marshall,
Welcome to SUSE LINUX Enterprise Server 9 (x86_64) - Kernel \r (\l).
The tail end of the polymake build, when it crashes, has the
following:
make[2]: Leaving directory
On 9/9/07, Dan Christensen [EMAIL PROTECTED] wrote:
But sage -t reports lots of errors, and spent an hour or two in
sage -t devel/doc-2.8.4.1/ref/sage.misc.trace.tex
before I killed it. If these errors are surprising, let me know and
From sage -help
-t files|dir-- test examples in
13 matches
Mail list logo
