Hi Jeroen,
On Mon, Oct 11, 2010 at 7:25 AM, Jeroen Demeyer wrote:
> That doesn't work for me with the version of Sphinx in sage-4.6.alpha3.
> It just literally writes the text
> ".. code-block:: cython" in the output...
This looks like we need to upgrade Sphinx (and possibly Pygments as
well).
On 2010-10-11 00:40, Dr. David Kirkby wrote:
> IMHO, something that touches so many files, that's not a bug fix but
> just renaming a command, has a fairly large risk/benefit factor.
It's true that it's not a bug fix by itself, but it prepares the way for
#9678 which will certainly fix bugs.
I'm
> It looks like the top level binomial() function is a mess already.
>
> - binomial does not accept variable when only in the lower argument
> http://trac.sagemath.org/sage_trac/ticket/9634
>
> - binomial does not accept float
> http://trac.sagemath.org/sage_trac/ticket/9633
Oh, y
I find the above error message, which can be generated in tons of different ways
rather amusing. How can one have less than 0 arguments?
Here's one command that gives this error, but there are several hundred of them.
sage: catalan(11)
---
On 10/11/10 12:05 AM, Mike Hansen wrote:
On Sun, Oct 10, 2010 at 3:51 PM, Dr. David Kirkby
wrote:
sage: macaulay2_console()
sh: line 1: M2: not found
Is "M2" supposed to be an optional package, or something like that? If so we
should state so in the help.
Yes, M2 is optional so "macaulay2_c
On Sun, Oct 10, 2010 at 3:51 PM, Dr. David Kirkby
wrote:
> sage: macaulay2_console()
> sh: line 1: M2: not found
>
> Is "M2" supposed to be an optional package, or something like that? If so we
> should state so in the help.
Yes, M2 is optional so "macaulay2_console()" will only work if the M2
ex
What's this supposed to do?
sage: macaulay2_console()
sh: line 1: M2: not found
Is "M2" supposed to be an optional package, or something like that? If so we
should state so in the help.
sage: help(macaulay2_console)
gives me the following.
Help on function macaulay2_console in module sage.
On 10/10/10 11:27 PM, Mitesh Patel wrote:
On 10/10/2010 11:54 AM, Jeroen Demeyer wrote:
As part of the "rewrite interrupt handling" ticket #9678, I decided that
_sig_on should be an *inline function* instead of a macro (one very good
reason for this would be that we can declare it cdef inline in
On 10/10/2010 11:54 AM, Jeroen Demeyer wrote:
> As part of the "rewrite interrupt handling" ticket #9678, I decided that
> _sig_on should be an *inline function* instead of a macro (one very good
> reason for this would be that we can declare it cdef inline int sig_on()
> except -1 in order to use
Hi Francois,
On Thu, 07 Oct 2010 22:39:38 +0200
Francois Maltey wrote:
> Now I want to test an expression with the binomial function call.
>
> y = binomial (3*x, x)# is fine
> op = y.operator() # is also fine
> op # I get binomial
> op == binomial
You're right... I really should go to bed now =)
Well then it works also for ubuntu ^^
-maldun
On 10 Okt., 23:07, Mike Hansen wrote:
> On Sun, Oct 10, 2010 at 2:05 PM, maldun wrote:
> > Thanks to your patch the segfault is now gone, but apperently a new
> > problem arises:
>
> That is what is s
On Sun, Oct 10, 2010 at 9:46 PM, Jeroen Demeyer wrote:
> On 2010-10-10 22:40, John Cremona wrote:
>> The file
>> file:///home/john/sage-4.6.alpha3/devel/sage-main/doc/output/html/en/reference/sage/interfaces/mwrank.html
>> is fine but from the notebook, the file
>> http://localhost:8000/doc/live
On Sun, Oct 10, 2010 at 2:05 PM, maldun wrote:
> Thanks to your patch the segfault is now gone, but apperently a new
> problem arises:
That is what is supposed to happen. There's no way to convert (x-a)
to a polynomial over the reals since "-a" cannot be converted to a
real number.
--Mike
--
On 10 Okt., 20:47, Mike Hansen wrote:
> On Sun, Oct 10, 2010 at 11:15 AM, maldun wrote:
> > sage: sage: a = var('a')
> > sage: sage: R. = a.parent()[]
> > sage: sage: (x - a).change_ring(RR) # boom!
>
> I've posted a patch athttp://trac.sagemath.org/sage_trac/ticket/10100
> which fixes this.
>
>
On 2010-10-10 22:40, John Cremona wrote:
> The file
> file:///home/john/sage-4.6.alpha3/devel/sage-main/doc/output/html/en/reference/sage/interfaces/mwrank.html
> is fine but from the notebook, the file
> http://localhost:8000/doc/live/reference/sage/interfaces/mwrank.html
> is not.
I believe it
On Sun, Oct 10, 2010 at 9:27 PM, Jeroen Demeyer wrote:
> On 2010-10-10 22:23, John Cremona wrote:
>>> Works for me, maybe there is something wrong with your Sphinx setup?
>>
>> I didn't know I had a Sphinx setup!?
>
> Well, as part of Sage, that is. Have you tried rebuilding Sage from
> scratch?
On 2010-10-10 22:23, John Cremona wrote:
>> Works for me, maybe there is something wrong with your Sphinx setup?
>
> I didn't know I had a Sphinx setup!?
Well, as part of Sage, that is. Have you tried rebuilding Sage from
scratch?
--
To post to this group, send an email to sage-devel@googlegro
On 10/10/10 09:19 PM, Jeroen Demeyer wrote:
On 2010-10-10 22:15, John Cremona wrote:
When I look at the reference manual (html) built with 4.6.alpha3, the
"sage: " prompts are missing.
So I checked with several recent versions, and see the same (no
prompts), using both chrome and firefox (linux
On 2010-10-10 19:38, Mike Hansen wrote:
> You can do
>
> .. code-block:: cython
>
>cdef i
That doesn't work for me with the version of Sphinx in sage-4.6.alpha3.
It just literally writes the text
".. code-block:: cython" in the output...
--
To post to this group, send an email to sage-dev
On Sun, Oct 10, 2010 at 9:19 PM, Jeroen Demeyer wrote:
> On 2010-10-10 22:15, John Cremona wrote:
>> When I look at the reference manual (html) built with 4.6.alpha3, the
>> "sage: " prompts are missing.
>>
>> So I checked with several recent versions, and see the same (no
>> prompts), using both
On 10/10/10 06:18 PM, maldun wrote:
8131979/home/maldun/sage/sage-4.5.3/devel/sage-
numpy-1.5/build/sage/finance/fractal.so
Program received signal SIGABRT, Aborted.
0x76e2ba75 in *__GI_raise (sig=) at ../
nptl/sysdeps/unix/sysv/linux/raise.c:64
64 ../nptl/sysdeps
On 2010-10-10 22:15, John Cremona wrote:
> When I look at the reference manual (html) built with 4.6.alpha3, the
> "sage: " prompts are missing.
>
> So I checked with several recent versions, and see the same (no
> prompts), using both chrome and firefox (linux). Has anyone else seen
> this?
Wor
When I look at the reference manual (html) built with 4.6.alpha3, the
"sage: " prompts are missing.
So I checked with several recent versions, and see the same (no
prompts), using both chrome and firefox (linux). Has anyone else seen
this?
John
--
To post to this group, send an email to sage-d
On Sun, Oct 10, 2010 at 11:15 AM, maldun wrote:
> sage: sage: a = var('a')
> sage: sage: R. = a.parent()[]
> sage: sage: (x - a).change_ring(RR) # boom!
I've posted a patch at http://trac.sagemath.org/sage_trac/ticket/10100
which fixes this.
--Mike
--
To post to this group, send an email to s
Ok I know your problem. I use ubuntu 10.04 myself.
I built my own valgrind with source from svn to get it running.
Since we have the quite the same system I tried it out myself, and
voila...
valgrind gives no valuable information, except that it's a segfault:
sage: sage: a = var('a')
sage: sage
Ok I know your problem. I use ubuntu 10.04 myself.
I built my own valgrind with source from svn to get it running.
Since we have the quite the same system I tried it out myself, and
voila...
valgrind gives no valuable information, except that it's a segfault:
sage: sage: a = var('a')
sage: sage
On Sun, Oct 10, 2010 at 12:55 AM, Jeroen Demeyer wrote:
> Does anybody know how to have syntax highlighting for Cython code in
> Sage? Clearly the code exists, because the official Cython
> documentation (see for example
> http://docs.cython.org/src/tutorial/external.html) is properly syntax
> hi
Ok I know your problem. I use ubuntu 10.04 myself.
I built my own valgrind with source from svn to get it running.
Since we have the quite the same system I tried it out myself, and
voila...
valgrind gives no valuable information, except that it's a segfault:
sage: sage: a = var('a')
sage: sage
Dear sage-devel,
As part of the "rewrite interrupt handling" ticket #9678, I decided that
_sig_on should be an *inline function* instead of a macro (one very good
reason for this would be that we can declare it cdef inline int sig_on()
except -1 in order to use Cython's exception propagation mecha
Ok then they didn't upgrade the valgrind package in the meantime.
I'm using Ubuntu myself and had the same problem, but I build my own
package with the latest source from svn. It worked for me
I can send it to you if you want, and you test it out.
maldun
On 7 Okt., 20:07, Johannes wrote:
> im s
I think this has an explanation: of all the matrix groups, SL(2,Z)
plays a vitally important role in the kind of number theory algorithms
which many Sage developers, including -- crucially -- William Stein,
in which it is absolutely essential to have efficient special-purpose
code which does not
Hi,
Is there a precise convention in Sage for construction and standard
methods of matrices ? The following is a little bit confusing.
1) Arguments as list / list of rows
-
{{{
sage: SL(2,ZZ)([[1,0],[0,1]])
[1 0]
[0 1]
sage: SL2Z([[1,0],[0,1]])
...
TypeErr
#10105 needs a very simple review -- David Kirby has tested the
(simple) patch thoroughly but we need someone who knows python to give
it the thumbs up. Thanks!
John
On Sat, Oct 9, 2010 at 8:07 PM, John Cremona wrote:
> Thanks to both -- I'll do thatdone. And perhaps one of you can
> revie
Hello,
Does anybody know how to have syntax highlighting for Cython code in
Sage? Clearly the code exists, because the official Cython
documentation (see for example
http://docs.cython.org/src/tutorial/external.html) is properly syntax
highlighted. So either this is not included in Sage or it is
34 matches
Mail list logo
