Hello,
> > > In this
> > > system, "==" is used to create equations, not to test equality.
> >
> > That's nasty!
for me that also seems potential source of confusion
maybe "===" would be better for equations?
as much as I remember, maxima uses "=", so "==" also doesn't help
maxima users a lot.
On Feb 8, 2008 2:21 AM, Simon King <[EMAIL PROTECTED]> wrote:
>
> Dear John,
>
> On 8 Feb., 10:40, "John Cremona" <[EMAIL PROTECTED]> wrote:
> > In this
> > system, "==" is used to create equations, not to test equality.
>
> That's nasty!
>
> My personal opinion is: When i say "==" in Sage then i
Kate wrote:
Hi Kate,
> Using 2.10.1, the following two pieces of
> code caused failures:
>
> a0 = matlab('eye(50)')
> a1 = matrix(ZZ,a0) # crashes
>
>
> a00 = str(mathlab('mat2str(eye(50))'))
> a01 = a00.replace(' ',',').replace(';','],[')
> a02 = '[' + a01 = ']'
> a03 = eval(a02)
> a1 =
The function
random_prime(n)
returns differing types of objects. When n is 2, it returns a Sage
integer. When n is > 2, it returns a Python integer. A look at the
source code gives the impression that it should return a Sage
integer.
Perhaps devel/sage-main/sage/rings/arith.py line 907 should
I'm having some trouble doctesting non sage files. The only things I
could find in the Programming Guide were:
4.3.1 Testing .py, .pyx and .sage Files
Run sage -t to test that all code examples in
filename.py. Similar remarks apply to .sage and
.pyx files.
and
5.3.8 Doctest
Using 2.10.1, the following two pieces of
code caused failures:
a0 = matlab('eye(50)')
a1 = matrix(ZZ,a0) # crashes
a00 = str(mathlab('mat2str(eye(50))'))
a01 = a00.replace(' ',',').replace(';','],[')
a02 = '[' + a01 = ']'
a03 = eval(a02)
a1 = matrix(zz,a03)
a2 = matlab.sage2matlab_matr
> Date: Thu, 7 Feb 2008 18:18:20 -0800 (PST)
> From: Marshall Buck <[EMAIL PROTECTED]>
>
> R. = GF(2)[]
>
> f = x^5+x^2+1
>
> fx = ntl.GF2X(f)
>
> gives error:
>
> Traceback (most recent call last):fx
> File "ntl_GF2X.pyx", line 141, in
> sage.libs.ntl.ntl_GF2X.ntl_GF2X.__init__
> Attri
Hello,
> You and John explained that "x==x" returns an equation since the
> underlying maxima system does.
> So, why does maxima('x')==maxima('x') return True?
> And why maxima('x==x') freezes?
When John said that the underlying system (maxima) uses that
construction, he didn't mean it _literall
Dear Mike,
On 8 Feb., 10:58, "Mike Hansen" <[EMAIL PROTECTED]> wrote:
> This is the desired behavior in Sage with symbolic objects -- it
> returns the equation you specified. You can get a Boolean with
> bool().
Thank you! However, i was (and am) quite confused that such explicit
evaluation is
Dear John,
On 8 Feb., 10:40, "John Cremona" <[EMAIL PROTECTED]> wrote:
> In your first example, where you have not defined x, ...
... but it is pre-defined, and explicitly saying "var('x')" has the
same effect.
> In this
> system, "==" is used to create equations, not to test equality.
That's
Hi Simon,
> That's to say, the expressions are displayed in the same canonical
> form, but "==" does not return True.
This is the desired behavior in Sage with symbolic objects -- it
returns the equation you specified. You can get a Boolean with
bool().
sage: eq = ((-x^4-1)/(x^2)) == ((x^4+1)/
Hi,
I made those
http://trac.sagemath.org/sage_trac/ticket/2105
and
http://trac.sagemath.org/sage_trac/ticket/2106
respectively. Thanks for reporting this!
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_www: http://www.inform
It's a feature.
In your first example, where you have not defined x, it is treated as
a symbol and the expressions you create using x are purely symbolic;
in fact they are objects within the underlying maxima system. In this
system, "==" is used to create equations, not to test equality. And
in
Dear Sage team,
i met the following bug/feature:
sage: ((-x^4-1)/(x^2)) == ((x^4+1)/((-1)*x^2))
(-x^4 - 1)/x^2 == (-x^4 - 1)/x^2
That's to say, the expressions are displayed in the same canonical
form, but "==" does not return True.
Is this worth a ticket?
Another potential
14 matches
Mail list logo
