On Feb 15, 2008 9:57 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
>
>
> David Joyner wrote:
> > On Fri, Feb 15, 2008 at 12:43 PM, John Cremona <[EMAIL PROTECTED]> wrote:
> >> I think both/either of these are useful enough they should be
> >> included. In David's code I noticed that he had to shif
On 16/02/2008, David Kohel <[EMAIL PROTECTED]> wrote:
>
> Hi John,
>
> > I'm not sure I understand the end of your message. Nowhere does the
> > code I have in mind assume that anything is cyclic, let alone of prime
> > order: the bsgs and dlog functions will terminate if there is no
> > solutio
Wow, that's ambitious. Thanks for all the work on that front.
I have a comment that is a little off-topic but perhaps relevant.
After talking to some people at the joint meetings in San Diego, and
especially after using Sage a lot in the classroom this semester, I've
been struck by the following
I would like to report a minor problem compiling sage
---
* my environment:
laptop running Fedora 2.6.23.15-137.fc8
with the intle mkl libraries (blas, lapack) installed
environmental variables CPPFLAGS and LDFLAGS
are set to point to the intel include and lib director
On Feb 16, 11:55 am, Jason Grout <[EMAIL PROTECTED]> wrote:
> What I'm trying to do is get a number field that has all the roots of a
> (not necessarily irreducible) polynomial.
There is code to do this embedded in qqbar.py.
sage: x = polygen(QQ)
sage: b = (x^2-2)*(x^2-3)
sage: rts = b.roots(rin
Thanks, Carl -- I had been thinking that in Magma I would have done
just this using its AlgebraicallyClosedField, but did not realise that
we had this in Sage too. Now I'll go and look at what it has
OK, so the first thing I tried (sorry) caused a crash. I'll file a
ticket for this: #2194
Thank you for the quick response!
I used MKL for historical reasons
unrelated to performance...
I think I will undefine CPPFLAGS and LDFLAGS
to ensure the sage build process does not pick
up my MKL installation.
That leaves my original question:
since I need
--with-recommended-
On Feb 17, 3:50 pm, Gerhard Ertaler <[EMAIL PROTECTED]> wrote:
> I would like to report a minor problem compiling sage
> ---
> * my environment:
Hi Gerhard,
> laptop running Fedora 2.6.23.15-137.fc8
>
> with the intle mkl libraries (blas, lapack) installed
>
> environmental
Carlo,
I'm forwarding this to sage-devel.
-- Forwarded message --
From: Carlo Hamalainen <[EMAIL PROTECTED]>
Date: Feb 17, 2008 10:20 AM
Subject: pyx-0.10 package
To: William Stein <[EMAIL PROTECTED]>
Hi,
I made a spkg for PyX-0.10 since 0.8.1 didn't work on Sage 2.10 for me.
My fault, I reported it but didn't open a ticket. I'll wait for Carl
to do so to avoid duplication. I have another of my own to open
(complete with patch).
John
On 17/02/2008, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Feb 11, 12:14 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> > On Feb 10,
On Feb 11, 12:14 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> On Feb 10, 6:58 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
>
>
> > First the bad news:
> > --
> > | SAGE Version 2.10.1, Release Date: 2008-02-02
Marshall wrote:
> I have a comment that is a little off-topic but perhaps relevant.
> After talking to some people at the joint meetings in San Diego, and
> especially after using Sage a lot in the classroom this semester, I've
> been struck by the following fact: people who use Sage who are new
From Carlo's blog:
> The previous pyx spkg tried to put the pyxrc file into /etc but I
> prefer to run Sage as a normal user, and sudo-ing to install a
> package isn’t completely straightforward (you have to set some
> environment variables, so it’s not newbie-friendly). I made my spkg-
>
> So my suggestion is that it might be worthwhile to
> mark up Sage examples for newbies so that pre-defined words such as
> "for" and "in" are highlighted somehow.
Are you suggesting that new programmers start with Emacs and font-
lock-mode? What a good idea :)
Thoroughly tongue-in-cheek,
Nic
On Feb 17, 10:44 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> My fault, I reported it but didn't open a ticket. I'll wait for Carl
> to do so to avoid duplication. I have another of my own to open
> (complete with patch).
OK, this is now #2195.
Carl
--~--~-~--~~~--
On Feb 17, 7:13 pm, gerhard <[EMAIL PROTECTED]> wrote:
Hi Gerhard,
> Thank you for the quick response!
> I used MKL for historical reasons
> unrelated to performance...
Ok, interesting to know.
> I think I will undefine CPPFLAGS and LDFLAGS
> to ensure the sage build process does not pick
>
...and I have given it a positive review. If only life were always
this easy. Thanks!
John
On 17/02/2008, Carl Witty <[EMAIL PROTECTED]> wrote:
>
> On Feb 17, 10:18 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> > Thanks, Carl -- I had been thinking that in Magma I would have done
> > just th
On Feb 17, 10:18 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Thanks, Carl -- I had been thinking that in Magma I would have done
> just this using its AlgebraicallyClosedField, but did not realise that
> we had this in Sage too. Now I'll go and look at what it has
>
> OK, so the first thi
On Feb 17, 7:55 pm, Carl Witty <[EMAIL PROTECTED]> wrote:
> On Feb 17, 10:44 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
> > My fault, I reported it but didn't open a ticket. I'll wait for Carl
> > to do so to avoid duplication. I have another of my own to open
> > (complete with patch).
On Feb 17, 2008 7:56 PM, Nick Alexander <[EMAIL PROTECTED]> wrote:
> I suggest in ~/.sage. Is that reasonable?
Sounds good, I've ammended the package at
http://carlo-hamalainen.net/sage/pyx-0.10.spkg
to put pyxrc into $HOME/.sage/etc/pyxrc. The etc prefix comes about
because I'm using
python
On Feb 17, 9:37 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> What's the exact rule for who gets emailed any changes to a trac ticket?
The owner, reporter and anybody who commented on the ticket should get
updates.
> I would be nice if anyone who had ever made a comment was added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Cremona wrote:
| What's the exact rule for who gets emailed any changes to a trac ticket?
|
| I would be nice if anyone who had ever made a comment was added to the
| ticket's mailing list -- e.g. someone who has reviewed a patch.
| (Maybe this h
On Feb 17, 2008 12:41 PM, Alex Ghitza <[EMAIL PROTECTED]> wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> John Cremona wrote:
> | What's the exact rule for who gets emailed any changes to a trac ticket?
> |
> | I would be nice if anyone who had ever made a comment was added to the
>
On Feb 17, 9:53 pm, Nick Alexander <[EMAIL PROTECTED]> wrote:
> On 17-Feb-08, at 12:35 PM, John Cremona wrote:
>
> > ... and have done.
>
> > Incidentally, everyt ime that ticket gets changed, I get an email
> > about it; if you did too then we would not need to email eachother
> > separately a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Stein wrote:
| On Feb 17, 2008 12:41 PM, Alex Ghitza <[EMAIL PROTECTED]> wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> John Cremona wrote:
|> | What's the exact rule for who gets emailed any changes to a trac
ticket?
|> |
|
On Feb 17, 10:04 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> | Dumb question -- how is that possible? When I create
> | new trac users I don't enter email addresses anywhere,
> | so by default trac doesn't know valid email accounts associated
> | to users.
What's the exact rule for who gets emailed any changes to a trac ticket?
I would be nice if anyone who had ever made a comment was added to the
ticket's mailing list -- e.g. someone who has reviewed a patch.
(Maybe this happens already?)
Apart from that, would it be possible for others to set a
On 17-Feb-08, at 12:35 PM, John Cremona wrote:
> ... and have done.
>
> Incidentally, everyt ime that ticket gets changed, I get an email
> about it; if you did too then we would not need to email eachother
> separately as well.
I was unsure if you did. I really wish it was clearer who was 'i
Hi Jaap,
I went ahead and fixed (I hope!) the doctest below. (I just added a
prec flag, and made the doctests use it, so this should avoid any sort
of architecture-dependent issues). Could you try this out and let me
know if it works, and then give the patch a positive review? Thanks!
If anyone
29 matches
Mail list logo
