On Mon, 20 Aug 2007 23:13:43 +0200
Martin Albrecht <[EMAIL PROTECTED]> wrote:
>
> > I view "then" as being about Jan 1, 2008. It would be great to
> > have SAGE-3.0 available when I'm at the AMS meeting in San
> > Diego.So "3 months" is the sort of time frame I have in mind.
> > Is that re
I definitely think it's a good idea, because SAGE (or at least
SAGElite) should be just like any other package - it should install in
a standard way, there should be a regular Debian/Ubuntu package etc.
and it should compete with all the other opensource programs in Debian
main.
Matplotlib is ver
On 8/20/07, William Stein <[EMAIL PROTECTED]> wrote:
>
> I want to create a "SAGE lite" version of SAGE. This is inspired by
> the following:
>
>* OLPC
>* Porting SAGE to run on certain architectures is very hard
>* Changing SAGE so it installs into a system-wide Python is hard.
>
On 8/20/07, didier deshommes <[EMAIL PROTECTED]> wrote:
>
> 2007/8/20, didier deshommes <[EMAIL PROTECTED]>:
> Updated spkg for sympow here:
> http://sage.math.washington.edu/home/dfdeshom/sympow-1.018.1.p2.spkg
Thanks -- I've tested this on Solaris and it works for me. I'll include
it in the ne
Mark (cc: sage-devel)
Do you have any comments on the remarks below about sympow?
In particular, "Otherwise, sympow would be useless on
anything not linux and not x86." Given that you only use x86,
and are perhaps the main user of sympow... ?
-- Forwarded message --
From: didie
2007/8/20, didier deshommes <[EMAIL PROTECTED]>:
Updated spkg for sympow here:
http://sage.math.washington.edu/home/dfdeshom/sympow-1.018.1.p2.spkg
didier
> 2007/8/20, mabshoff <[EMAIL PROTECTED]>:
> > Yeah, I think that sympow uses extended precision for doubles. I never
> > ran properly on Cyg
2007/8/20, mabshoff <[EMAIL PROTECTED]>:
> Yeah, I think that sympow uses extended precision for doubles. I never
> ran properly on Cygwin on x86 cpus, so I am somewhat worried on
> getting this to run properly on Sparc without some freaky gcc flags or
> some sparc assembly. I don't think it is hi
I sort of think that SAGE lite and Knoboo would be useless for OLPC
because there is already an unified software interface called Sugar
and a wiki environment based around Media Wiki for the project. I
don't see any point in using a whole new interface inside Sugar just
to do math that would be si
On 8/20/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
> > Wrong. The notebook is fully functional in pure python, as is DSAGE,
> > and as is all of the interfaces to Gap, maxima, etc.
>
> I guess I should have said "doing much *math*" because I agree that
> there is tons of non-math functionalit
On 8/20/07, David Harvey <[EMAIL PROTECTED]> wrote:
> My first impression of this idea is mostly negative, but I'm
> interested to see where this goes.
>
> Will SAGElite use the preparser? That would be a problem if Integer
> (2) appears somewhere, and Integer is not defined. If you want
> calcul
On Aug 20, 2007, at 4:53 PM, William Stein wrote:
> On 8/20/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>> I can't imagine SAGE doing much (as it is now) in pure python--for
>> example we wouldn't even have Integer.pyx.
>
> Wrong. The notebook is fully functional in pure python, as is DSAGE,
My first impression of this idea is mostly negative, but I'm
interested to see where this goes.
Will SAGElite use the preparser? That would be a problem if Integer
(2) appears somewhere, and Integer is not defined. If you want
calculus/plotting then presumably you want people to be able to e
On Aug 21, 2:11 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 8/20/07, alex clemesha <[EMAIL PROTECTED]> wrote:
>
> > > *unless* we actually start providing some math functionality.
>
> > Isn't SAGE "math functionality"? :)
>
> It is definitely not the case that SAGE is only "math functio
On 8/20/07, alex clemesha <[EMAIL PROTECTED]> wrote:
> > *unless* we actually start providing some math functionality.
>
> Isn't SAGE "math functionality"? :)
It is definitely not the case that SAGE is only "math functionality".
The Notebook GUI, the interfaces to other programs, and DSage
all a
>
> *unless* we actually start providing some math functionality.
Isn't SAGE "math functionality"? :)
Those who where at SAGE days 4 might remember that Dorian
and I have already spent a bunch of effort working on a general
notebook interface to Python and theoretically any other interpreted
la
On 8/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > The question is what should go in SAGE lite. Thoughts? I think the
> > key constraints
> > should be:
> > 1. SAGE lite is pure Python
> > 2. Dependence on twisted and pexpect 2.0 is fine.
>
Another very natural thing to put in sag
On 8/20/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
> I can't imagine SAGE doing much (as it is now) in pure python--for
> example we wouldn't even have Integer.pyx.
Wrong. The notebook is fully functional in pure python, as is DSAGE,
and as is all of the interfaces to Gap, maxima, etc.
> E
> The question is what should go in SAGE lite. Thoughts? I think the
> key constraints
> should be:
> 1. SAGE lite is pure Python
> 2. Dependence on twisted and pexpect 2.0 is fine.
Much of the core functionality of SAGE is written in Cython. Since it is a
stated goal of Cython to be sh
I can't imagine SAGE doing much (as it is now) in pure python--for
example we wouldn't even have Integer.pyx. Even the calculus package
has pyx files, and I would envision it getting more. The "lite" makes
it seem like the core is still there, and I don't see how to extract
that.
The only
On 8/20/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
> > Thoughts? Basically, the initial point of this is that if somebody
> > wants to use
> > SAGE just to talk with mathematica, or just for the notebook then they
> > can trivially do so. If they need serious math functionality, they
> > hav
> Thoughts? Basically, the initial point of this is that if somebody
> wants to use
> SAGE just to talk with mathematica, or just for the notebook then they
> can trivially do so. If they need serious math functionality, they
> have to install
> something more. In the long run though, with hel
Hi,
I want to create a "SAGE lite" version of SAGE. This is inspired by
the following:
* OLPC
* Porting SAGE to run on certain architectures is very hard
* Changing SAGE so it installs into a system-wide Python is hard.
* Many people could benefit from the SAGE interfaces (to Gap, M
On Mon, Aug 20, 2007 at 03:47:42PM -0700, William Stein wrote:
> I would very much appreciate someone fixing the singular spkg so flex and
> bison are never needed. Maybe we could touch the generated files in
> spkg-install
> right at the beginnig? It would be very nice to remove those two
> de
On 8/20/07, mabshoff <[EMAIL PROTECTED]> wrote:
> Yes, that is true, but if the timestamp of the generated file is older
> than say the bison input Make will rebuild it. One just needs to
> update the spkg after running bison and flex manually. But since the
> spkg-install checks for bison and fle
On Aug 21, 12:12 am, "Juan M. Bello Rivas" <[EMAIL PROTECTED]>
wrote:
> Hi,
> I'm not familiar with Singular, but after a quick look at the spkg I
> see the files generated by flex and bison are included in the package.
>
Yes, that is true, but if the timestamp of the generated file is older
Hi,
On Mon, Aug 20, 2007 at 02:28:04PM -0700, mabshoff wrote:
> > flex 2.5.33
> > bison 2.3
>
> That sounds about right. We had problems earlier with an older bison &
> the Singular 3.0.3
I'm not familiar with Singular, but after a quick look at the spkg I
see the files generated by flex and bis
didier deshommes wrote:
> 2007/8/20, mabshoff <[EMAIL PROTECTED]>:
>
> > The overall situation: Most major packets build, I believe sympow and
> > cvxopt are the remaining holdouts. cvxopt complains about a missing
> > complex.h. I know that there cvxopt binaries for Solaris - so any
> > ideas?
2007/8/20, mabshoff <[EMAIL PROTECTED]>:
> The overall situation: Most major packets build, I believe sympow and
> cvxopt are the remaining holdouts. cvxopt complains about a missing
> complex.h. I know that there cvxopt binaries for Solaris - so any
> ideas? sympow might be slightly harder to c
On Aug 20, 11:08 pm, "didier deshommes" <[EMAIL PROTECTED]> wrote:
> [I was going to post this on Trac as an "enhancement", but Trac seems
> to be down at the moment]
>
Hello,
trac is working for me at the moment.
> Hi,
> Current;y, the only official dependencies for SAGE are: "gcc, g++,
> ma
On 8/20/07, didier deshommes <[EMAIL PROTECTED]> wrote:
> [I was going to post this on Trac as an "enhancement", but Trac seems
> to be down at the moment]
I just checked and trac isn't down. If it ever does go down though, please
report immediately.
> Current;y, the only official dependencies
> And something completely different: There are people out there with
> little or no coding experience. But those people can help during Bug
> Days too by improving the Wiki or by trawling sage-support for "how do
> I" question (and answers) and add them somewhere to the
> documentation.
+1
This
> > Hi,
Hello,
>
> > I propose that the next SAGE bug squash even be Saturday, September 1,
> > which is
> > in two weeks. Whose interested?
>
> Looks like I'll miss that one too, as I'll be out of town for labor
> day weekend.
>
> > Those are just some ideas for what would make SAGE "3.0" ma
> I view "then" as being about Jan 1, 2008. It would be great to have
> SAGE-3.0 available when I'm at the AMS meeting in San Diego.So "3
> months" is the sort of time frame I have in mind. Is that reasonable for
> PolyBoRi?
I think so. The authors want to release it to the public by the e
[I was going to post this on Trac as an "enhancement", but Trac seems
to be down at the moment]
Hi,
Current;y, the only official dependencies for SAGE are: "gcc, g++,
make, m4, perl, ranlib, and tar" (in $SAGE_ROOT/README.txt). I'd like
to see these specified with a little more detail in the READ
On Aug 20, 10:56 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 8/20/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
>
And something completely different: There are people out there with
little or no coding experience. But those people can help during Bug
Days too by improving the Wiki or b
On 8/20/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
>
> > I would like to encourage everybody to post their top wishlist item; we'll
> > see what's popular (and realistic), and make those the milestones for
> > sage-3.0.
>
> I'd like to see PolyBoRi integrated by then. That would be a real kill
> I would like to encourage everybody to post their top wishlist item; we'll
> see what's popular (and realistic), and make those the milestones for
> sage-3.0.
I'd like to see PolyBoRi integrated by then. That would be a real killer
feature (for people like me). Also I want to have contributed
On 8/20/07, Dan Christensen <[EMAIL PROTECTED]> wrote:
> Nils Bruin <[EMAIL PROTECTED]> writes:
>
> > This makes me think that a checkbox "this worksheet is persistent"
> > might be better.
>
> This sounds good to me.
>
> I'm also curious what happens if I leave a browser open to a worksheet
> in
On 8/20/07, didier deshommes <[EMAIL PROTECTED]> wrote:
> 2007/8/20, William Stein <[EMAIL PROTECTED]>:
> >
> > Hi,
> >
> > I propose that the next SAGE bug squash even be Saturday, September 1,
> > which is
> > in two weeks. Whose interested?
>
> Looks like I'll miss that one too, as I'll be o
Nils Bruin <[EMAIL PROTECTED]> writes:
> This makes me think that a checkbox "this worksheet is persistent"
> might be better.
This sounds good to me.
I'm also curious what happens if I leave a browser open to a worksheet
in my office, and then open the worksheet again from home. Do they
someh
2007/8/20, William Stein <[EMAIL PROTECTED]>:
>
> Hi,
>
> I propose that the next SAGE bug squash even be Saturday, September 1, which
> is
> in two weeks. Whose interested?
Looks like I'll miss that one too, as I'll be out of town for labor
day weekend.
> Those are just some ideas for what
On Aug 20, 2007, at 2:07 PM, mabshoff wrote:
>> However, there is one "error" which valgrind reports on my own code
>> from time to time which I have been unable to determine the source
>> of.
>> It says something like "conditional jump depends on uninitialised
>> data". I have stared at code
2007/8/17, mabshoff <[EMAIL PROTECTED]>:
> ###
>
> flintqs-20070505: linux-ism for types. In lanzos.h add
>
> #ifdef __sun
> #define u_int32_t unsigned int
> #define u_int64_t unsigned long [?long?]
> #endif
>
> ##
On 8/20/07, mabshoff <[EMAIL PROTECTED]> wrote:
> I am. Date is fine, Saturday is also a good day because it lets one
> recover on Sunday.
>
> How does this relate to the 2.8.3 release date? I have started
I plan to release sage-2.8.3 on Friday, and for it to include new features.
Maybe 2.9 shoul
On Aug 20, 8:10 pm, Bill Hart <[EMAIL PROTECTED]> wrote:
> Getting rid of memory leaks also speeds up code dramatically as I
> found out recently. When new memory is allocated by the kernel, it
> isn't quite ready to be used. As you begin writing to it, pages of
> roughly 4kb at a time initiate
On Aug 20, 2007, at 9:18 AM, Nicholas Alexander wrote:
>
>> - A new "if you work on something it should be in trac" rule: Instead
>> of submitting patches directly to William you should create
>> tickets in
>> Sage's trac. So write William an Email and get a track account.
>> - I volunteered t
On Monday 20 August 2007, William Stein wrote:
> Hi,
>
> I propose that the next SAGE bug squash even be Saturday, September 1,
> which is in two weeks. Whose interested?
I am interested but it is highly unlikely I can attend: It is my moving
weekend. I should be settled the weekend after. I'd
On Aug 20, 2007, at 2:05 PM, William Stein wrote:
> I propose that the next SAGE bug squash even be Saturday, September
> 1, which is
> in two weeks. Whose interested?
>
> It might be fun for the Seattle-area people to all meet up in a common
> location for this.
I can probably be there. (I
On Aug 20, 8:05 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
Hello,
> I propose that the next SAGE bug squash even be Saturday, September 1, which
> is
> in two weeks. Whose interested?
I am. Date is fine, Saturday is also a good day because it lets one
recover on Sunday.
How does
Getting rid of memory leaks also speeds up code dramatically as I
found out recently. When new memory is allocated by the kernel, it
isn't quite ready to be used. As you begin writing to it, pages of
roughly 4kb at a time initiate an interrupt which the kernel has to
deal with, called a minor page
Hi,
I propose that the next SAGE bug squash even be Saturday, September 1, which is
in two weeks. Whose interested?
It might be fun for the Seattle-area people to all meet up in a common
location for this.
--
William Stein
Associate Professor of Mathematics
University of Washington
http://ww
On Aug 20, 6:18 pm, Nicholas Alexander <[EMAIL PROTECTED]> wrote:
> > - A new "if you work on something it should be in trac" rule: Instead
> > of submitting patches directly to William you should create tickets in
> > Sage's trac. So write William an Email and get a track account.
> > - I volun
Sage Enhancement Proposal - Valgrind & Sage integration: Hunting
memory leaks
Forward: Please excuse the rambling - I have meant to take more time
to write this up but had meetings all day and need to finish a couple
other work related things. Certain points may have been made more than
once and
> - A new "if you work on something it should be in trac" rule: Instead
> of submitting patches directly to William you should create tickets in
> Sage's trac. So write William an Email and get a track account.
> - I volunteered to take care of Sage's trac installation and do bug
> triage and atte
On 8/20/07, Jaap Spies <[EMAIL PROTECTED]> wrote:
> John Cremona wrote:
>
> >
> > While I'm here, where it says that in hg_sage.ci() the "ci" is short
> > for "commit", I think it's actually short for "check in" (thinking of
> > RCS rather than CVS...)
> >
>
> My fault.
Fix it all and send me a p
John Cremona wrote:
>
> While I'm here, where it says that in hg_sage.ci() the "ci" is short
> for "commit", I think it's actually short for "check in" (thinking of
> RCS rather than CVS...)
>
My fault.
Jaap Spies
--~--~-~--~~~---~--~~
To post to this group,
Actually, on that same page it talks about hg_log() while it really
means hg_sage.log()... That should be changed as well!
Paul
On Aug 20, 11:14 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Chapter 7 in the Progamming Guide, about using Mercurial, only
> mentions hg_sage but not hg_c_lib,h
Chapter 7 in the Progamming Guide, about using Mercurial, only
mentions hg_sage but not hg_c_lib,hg_doc, hg_extcode,
hg_scripts.I just discovered the existence of hg_extcode as I had
been editing some extcode! Now presumably I could rewrite that myself
using hg_doc and submit a patch
58 matches
Mail list logo
