Hi Simon,
>> Rename it, if that solves the problem.
I have done it. But I wonder why has that happened after upgrade from 4.7.2
to 4.8 (5.0beta4)?
Best regards,
Oleksandr
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage
Hi Oleksandr,
On 17 Feb., 21:52, Oleksandr Kazymyrov
wrote:
> Can anyone reproduce the same bug on Ubuntu?
The situation somehow reminds me a problem that I once had with a
wrapper of the C-MeatAxe (an implementation of matrices that I use it
in an optional Sage package). There was a C-function
Hi Simon,
It is very strange. I use Ubuntu 11.10 and my parameters are:
hamsin@hamsin-pc:~/bin/sage-5.0.beta4$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric
hamsin@hamsin-pc:~/bin/sage-5.0.beta4$ gcc --version
gcc (
Dear Oleksandr,
On 17 Feb., 15:32, Oleksandr Kazymyrov
wrote:
> Or just run "Main.sage" from a shell (in this case, variable PATH should
> has a path to the sage directory, like this one
> "PATH=/home/user/bin/sage/:$PATH").
Then I can not reproduce it.
I started a Sage shell, and did
Dear Simon,
>> But the only difference between the good and the bad version is that some
function is called PC in the bad file and PCc in the good file
Yes, exactly.
>> However, Oleksandr: What is one supposed to do in order to reproduce the
error? When I start a sage session and attach Main.sa
Hi Dima, hi Oleksandr,
On 17 Feb., 14:07, Dima Pasechnik wrote:
> I imagine the behaviour is similar to Python's, where it's jolly possible
> to do "list=2" and see stuff beginning to happen...
But the only difference between the good and the bad version is that
some function is called PC in the
In gmane.comp.mathematics.sage.support, you wrote:
> After upgrading from version 4.7.2 to 4.8, one function of dozen is stopped
> working. I use a combination of Sage + Cython. You can find examples in the
> attachments.
>
> The main problem is: when you use "PC" as the function name in "*.c" fi
Carl Witty wrote:
> On Mar 6, 12:53 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
>> As another option, though, how about
>> having the S or Sage namespace include all of the global namespace (at
>> least the default global namespace), so that S.pi (or Sage.pi) would
>> always refer to the sage syste
On Thu, Mar 6, 2008 at 4:15 PM, Carl Witty <[EMAIL PROTECTED]> wrote:
>
> On Mar 6, 3:46 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> > I think the real problem here is that Sage by default has so many
> > identifiers in the global namespace. I don't really like having so
> > many names there
On Mar 6, 3:46 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> I think the real problem here is that Sage by default has so many
> identifiers in the global namespace. I don't really like having so
> many names there. I think it was a deliberate design decision in
> python to keep the global namespa
On Mar 6, 2008, at 6:14 PM, Hector Villafuerte wrote:
>> That one *does* currently give a syntax error, because lambda really
>> is a python keyword. But there aren't too many python keywords. Off
>> the top of my head:
>
> Hi David, I'm aware of that behavior currently happening (the syntax
On Mar 6, 12:53 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
> As another option, though, how about
> having the S or Sage namespace include all of the global namespace (at
> least the default global namespace), so that S.pi (or Sage.pi) would
> always refer to the sage system pi (as opposed to havi
On Thu, Mar 6, 2008 at 5:05 PM, David Harvey <[EMAIL PROTECTED]> wrote:
>
>
> On Mar 6, 2008, at 5:56 PM, Hector Villafuerte wrote:
...
> > Yep, that's what I meant (reserved words, aka keywords); to expect
> > behavior like this:
> >
> > sage: lambda = 5
> > Syntax Error:
> > lambda =
On Mar 6, 2008, at 5:56 PM, Hector Villafuerte wrote:
>
>> On Thu, Mar 6, 2008 at 12:53 PM, Jason Grout
>> <[EMAIL PROTECTED]> wrote:
> ...
>>> What does "reserved words" mean? Do you mean that we should
>>> throw an
>>> error when those variables are assigned? I don't think that
>>> w
> On Thu, Mar 6, 2008 at 12:53 PM, Jason Grout
> <[EMAIL PROTECTED]> wrote:
...
> > What does "reserved words" mean? Do you mean that we should throw an
> > error when those variables are assigned? I don't think that would be
> > possible without some deep tinkering in python.
Hi Jason
On Thu, Mar 6, 2008 at 12:53 PM, Jason Grout
<[EMAIL PROTECTED]> wrote:
>
> Hector Villafuerte wrote:
> > Hi,
> > this just happened to me (maybe because I'm annoyingly slow today...):
> >
> > sage: var('t')
> > sage: x(t) = sin(2*pi*1000*t) + 1/2*sin(2*pi*2000*t + 3/4*pi)
> >
> > Exceptio
Hector Villafuerte wrote:
> Hi,
> this just happened to me (maybe because I'm annoyingly slow today...):
>
> sage: var('t')
> sage: x(t) = sin(2*pi*1000*t) + 1/2*sin(2*pi*2000*t + 3/4*pi)
>
> Exception (click to the left for traceback):
> ...
> TypeError: unsupported operand parent(s) for '*': '
17 matches
Mail list logo
