[sage-devel] Re: Factorial syntax

On Sep 1, 2009, at 11:34 PM, Dr. David Kirkby wrote: > > Dr. David Kirkby wrote: >> Dr. David Kirkby wrote: >> >>> Em, I thought I'd try this in Mathematica >>> >>> In[1]:= 5! >>> >>> Out[1]= 120 >>> >>> In[2]:= 5!! >>> >>> Out[2]= 15 >>> >>> In[3]:= 5!!! >>> >>> Out[3]= 1307674368000 >>> >>> In[

[sage-devel] Re: Factorial syntax

Dr. David Kirkby wrote: > Dr. David Kirkby wrote: > >> Em, I thought I'd try this in Mathematica >> >> In[1]:= 5! >> >> Out[1]= 120 >> >> In[2]:= 5!! >> >> Out[2]= 15 >> >> In[3]:= 5!!! >> >> Out[3]= 1307674368000 >> >> In[4]:= 5 >> >> Out[4]= 2027025 >> >> In[5]:= 5! >> >> >> >> Anyone

[sage-devel] Re: Factorial syntax

Dr. David Kirkby wrote: > Dr. David Kirkby wrote: > >> Em, I thought I'd try this in Mathematica >> >> In[1]:= 5! >> >> Out[1]= 120 >> >> In[2]:= 5!! >> >> Out[2]= 15 >> >> In[3]:= 5!!! >> >> Out[3]= 1307674368000 >> >> In[4]:= 5 >> >> Out[4]= 2027025 >> >> In[5]:= 5! >> >> >> >> Anyone

[sage-devel] Re: Factorial syntax

Dr. David Kirkby wrote: > Em, I thought I'd try this in Mathematica > > In[1]:= 5! > > Out[1]= 120 > > In[2]:= 5!! > > Out[2]= 15 > > In[3]:= 5!!! > > Out[3]= 1307674368000 > > In[4]:= 5 > > Out[4]= 2027025 > > In[5]:= 5! > > > > Anyone like to guess what it's doing? Trying t

[sage-devel] Re: Factorial syntax

Tom Boothby wrote: > On Mon, Aug 31, 2009 at 10:38 AM, Robert > Bradshaw wrote: >> As for the question at hand, I'm personally not convinced this is useful >> enough to merit another departure from pure Python. It also risks turning >> the valid Python expression "x!=120" into an invalid one (un

[sage-devel] Re: New graphics axes and gridlines

Alex Clemesha wrote: > Jason, > >> If you want a couple of reasons why we should delete our axes and >> gridlines code and instead shift that functionality to matplotlib, read >> the next section. > Thank you so much for putting in this effort!! When I wrote most of > the axes code, over 3 years

[sage-devel] Re: Factorial syntax

Hi, Out of curiosity, I want to ask why Sage has the syntax "R. = QQ[]" rather than "R = QQ[]"? It seems to me that the dot is redundant. Is it something the preparser cann't do? Kwankyu --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@go

[sage-devel] Re: New graphics axes and gridlines

Jason, > > If you want a couple of reasons why we should delete our axes and > gridlines code and instead shift that functionality to matplotlib, read > the next section. Thank you so much for putting in this effort!! When I wrote most of the axes code, over 3 years ago, matplotlib was considerab

[sage-devel] Re: whither the KAIST mirror?

Hi Dan, On Wed, Sep 2, 2009 at 12:12 PM, Dan Drake wrote: > Does anybody know what happened to the KAIST mirror? It's not listed on > the download pages, and http://ftp.kaist.ac.kr/sage/ is empty. Anyone > know why? I have no idea. Harald would probably know the cause. -- Regards Minh Van Nguy

[sage-devel] whither the KAIST mirror?

Does anybody know what happened to the KAIST mirror? It's not listed on the download pages, and http://ftp.kaist.ac.kr/sage/ is empty. Anyone know why? Dan -- --- Dan Drake - KAIST Department of Mathematical Sciences --- http://mathsci.kaist.ac.kr/~drake signature.asc Description:

[sage-devel] Re: CSS overflow:auto prevents printing

William Stein wrote: > > > 2009/9/1 Jason Grout > > > > William Stein wrote: > > > > > > On Tue, Sep 1, 2009 at 4:22 PM, Jason Grout > mailto:jason-s...@creativetrax.com> > >

[sage-devel] Re: Inequalities in InfinitePolynomialRing

William Stein wrote: > > > On Tue, Sep 1, 2009 at 6:44 PM, Minh Nguyen > wrote: > > > Hi Simon, > > On Tue, Sep 1, 2009 at 6:34 PM, Simon King > wrote: > > > > > I have no idea how one can solve inequalitie

[sage-devel] Re: CSS overflow:auto prevents printing

2009/9/1 Jason Grout > > William Stein wrote: > > > > > > On Tue, Sep 1, 2009 at 4:22 PM, Jason Grout > > wrote: > > > > > > I was trying to print a long worksheet in Firefox 3.5 and Opera 10.0 > on > > Ubuntu 9.04, and I was only getting a page or two

[sage-devel] Re: Inequalities in InfinitePolynomialRing

On Tue, Sep 1, 2009 at 6:44 PM, Minh Nguyen wrote: > > Hi Simon, > > On Tue, Sep 1, 2009 at 6:34 PM, Simon King wrote: > > > > > I have no idea how one can solve inequalities, though. That's not my > > field of expertise. > > I'm based in a department with a research group in mathematical > ineq

[sage-devel] Re: Inequalities in InfinitePolynomialRing

Hi Simon, On Tue, Sep 1, 2009 at 6:34 PM, Simon King wrote: > I have no idea how one can solve inequalities, though. That's not my > field of expertise. I'm based in a department with a research group in mathematical inequalities and applications, but ironically I don't know anything about so

[sage-devel] Re: CSS overflow:auto prevents printing

William Stein wrote: > > > On Tue, Sep 1, 2009 at 4:22 PM, Jason Grout > wrote: > > > I was trying to print a long worksheet in Firefox 3.5 and Opera 10.0 on > Ubuntu 9.04, and I was only getting a page or two before everything cut > off. I the

[sage-devel] Re: Sage-4.1.1 test fails for r-2.6.1.p23

Hi, On Tue, Sep 1, 2009 at 11:03 PM, samrat wrote: > > Hi, > > I am trying to compile sage 4.1.1 on my desktop: > P4, 2.66GHz, 2.25GB ram > Machine: Linux linux-hl2a 2.6.25.20-0.5-pae #1 SMP 2009-08-14 01:48:11 > +0200 i686 i686 i386 GNU/Linux > gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-br

[sage-devel] Re: Factorial syntax

On Mon, Aug 31, 2009 at 10:38 AM, Robert Bradshaw wrote: > > On Mon, 31 Aug 2009, William Stein wrote: > >> On Mon, Aug 31, 2009 at 8:23 AM, rjf wrote: >> >>> >>> You can either >>> (a) adhere to Python syntax. >>> (b) adhere to Python except for a few changes that are so subtle that >>> no one w

[sage-devel] Re: How do I apply a patch or clean up a repository?

Hi Stan, On Tue, Sep 1, 2009 at 10:38 PM, Stan Schymanski wrote: > > Thanks, John! > > Is there a simple step-by-step guide to safely applying patches > somewhere? Everyone seems to do it differently. I found the following > thread helpful, but it would be good to summarise it somewhere: > http:/

[sage-devel] Re: New graphics axes and gridlines

On Tue, Sep 1, 2009 at 4:11 PM, Jason Grout wrote: > > I've recently been working with Karl-Dieter on shifting our axes and > gridline functionality over to the corresponding matplotlib functions, > and exposing the matplotlib object a bit better. I think we are to the > point where we can use co

[sage-devel] Re: CSS overflow:auto prevents printing

On Tue, Sep 1, 2009 at 4:22 PM, Jason Grout wrote: > > I was trying to print a long worksheet in Firefox 3.5 and Opera 10.0 on > Ubuntu 9.04, and I was only getting a page or two before everything cut > off. I then changed the div.worksheet CSS style by deleting the > overflow:auto;. Then printi

[sage-devel] Re: New graphics axes and gridlines

Jason Grout wrote: > I've recently been working with Karl-Dieter on shifting our axes and > gridline functionality over to the corresponding matplotlib functions, > and exposing the matplotlib object a bit better. I think we are to the > point where we can use comments and a vote on a new stra

[sage-devel] CSS overflow:auto prevents printing

I was trying to print a long worksheet in Firefox 3.5 and Opera 10.0 on Ubuntu 9.04, and I was only getting a page or two before everything cut off. I then changed the div.worksheet CSS style by deleting the overflow:auto;. Then printing worked great (i.e., I could print out the 20-page work

[sage-devel] New graphics axes and gridlines

I've recently been working with Karl-Dieter on shifting our axes and gridline functionality over to the corresponding matplotlib functions, and exposing the matplotlib object a bit better. I think we are to the point where we can use comments and a vote on a new strategy for placing axes. Si

[sage-devel] List of doctest failures in current Mandriva sagemath

Hi, The package I am building uses newer versions of several components, and while I believe most of these tests probably are correct, I may be missing some patch, so, if you can confirm it is correct, or is an alternate correct response, please let me know. These are not the only errors, b

[sage-devel] Re: sage fails to build with user built python in PATH

Hi Minh! On Mon, Aug 31, 2009 at 7:24 PM, Minh Nguyen wrote: > > Hi Ondrej, > > On Tue, Sep 1, 2009 at 4:01 AM, Ondrej Certik wrote: >> >> Hi, >> >> we got this bugreport in femhub: >> >> http://groups.google.com/group/femhub/browse_thread/thread/1bfad9ea3ec7df48 >> >> and it turns out it is a Sa

[sage-devel] Re: Forward #sage-support to #sage-devel

> > Definitely keep the mailing lists separate--usually if you're told to   > go to devel than it's a more interesting/deeper question, but the   > bulk of sage-support does not belong there. > > As for the channels, is the concern that no one hangs out in #sage- > support? Yes, I was only referr

[sage-devel] Re: What units should process size & memory be returned in?

Note that MSVC is not ISO C99 compliant. Also note that some compilers do not support long long. It is much safer to use mp_limb_t. However the correct units to use would probably be uintptr_t. Here is what I think is pretty safe: Counter : ulong (typedef for unsigned long) unless one can be ab

[sage-devel] Re: Forward #sage-support to #sage-devel

On Tue, Sep 1, 2009 at 9:22 AM, Jason Grout wrote: > > Dr. David Kirkby wrote: > > Ahmed Fasih wrote: > >> buntfalke made a good suggestion yesterday and I bring it to your > >> attention: can we merge the #sage-devel and #sage-support channels by > >> forwarding all connections to #sage-support t

[sage-devel] Re: Forward #sage-support to #sage-devel

Dr. David Kirkby wrote: > Ahmed Fasih wrote: >> buntfalke made a good suggestion yesterday and I bring it to your >> attention: can we merge the #sage-devel and #sage-support channels by >> forwarding all connections to #sage-support to #sage-devel? > > > I'm not so sure that is a good idea. Sup

[sage-devel] Re: barriers to community growth

On Fri, Jul 24, 2009 at 07:24:22AM -0700, William Stein wrote: > * Have you identified the three or four most likely changes a developer will > need to make, and tailored developer guides for those tasks? > > No, that would be a good idea for a tutorial.What are they? >* add a new functi

[sage-devel] Re: What units should process size & memory be returned in?

On Sep 1, 2009, at 9:17 AM, William A. Stein wrote: > On Sep 1, 2009, at 6:11 AM, David Kirkby wrote: > >> >> 2009/9/1 gsw : >>> >>> Hi Dave, >>> >>> I'd propose to use ISO C99 notation from "Stdint.h", e.g. >>> "uint64_t", >>> and do the count in bytes. >>> This standard notation is even usabl

[sage-devel] Re: Forward #sage-support to #sage-devel

On Sep 1, 2009, at 9:23 AM, kcrisman wrote: > On Sep 1, 11:59 am, "Dr. David Kirkby" > wrote: >> Ahmed Fasih wrote: >>> buntfalke made a good suggestion yesterday and I bring it to your >>> attention: can we merge the #sage-devel and #sage-support >>> channels by >>> forwarding all connections

[sage-devel] Re: Forward #sage-support to #sage-devel

On Sep 1, 11:59 am, "Dr. David Kirkby" wrote: > Ahmed Fasih wrote: > > buntfalke made a good suggestion yesterday and I bring it to your > > attention: can we merge the #sage-devel and #sage-support channels by > > forwarding all connections to #sage-support to #sage-devel? > > I'm not so sure

[sage-devel] Re: What units should process size & memory be returned in?

On Sep 1, 2009, at 6:11 AM, David Kirkby wrote: > > 2009/9/1 gsw : >> >> Hi Dave, >> >> I'd propose to use ISO C99 notation from "Stdint.h", e.g. "uint64_t", >> and do the count in bytes. >> This standard notation is even usable on Windows. >> (See also http://en.wikipedia.org/wiki/Stdint.h) >>

[sage-devel] Re: Forward #sage-support to #sage-devel

Ahmed Fasih wrote: > buntfalke made a good suggestion yesterday and I bring it to your > attention: can we merge the #sage-devel and #sage-support channels by > forwarding all connections to #sage-support to #sage-devel? I'm not so sure that is a good idea. Support and developers are two entire

Re: [codenode-devel] Re: [sage-devel] Re: grant proposal season

On Tue, Sep 1, 2009 at 4:13 AM, Alex Ghitza wrote: > > On Tue, Sep 1, 2009 at 8:50 PM, Dr. David Kirkby > wrote: >> >> Ondrej Certik wrote: >> >>> Another idea is something like wolfram alpha: >>> it's on my todo to do something like "sympy gamma". And then something >>> for femhub (femhub.org) a

[sage-devel] Re: Forward #sage-support to #sage-devel

On Sep 1, 4:59 pm, Ahmed Fasih wrote: > Yup, a channel op can set this up pretty easily: > > http://freenode.net/policy.shtml#channelforwarding > Could you do this? And add me and others as channel owners? I think we should also register #sage-devel as an official channel. I once looked at fre

[sage-devel] Re: Sage events in Europe this year?

On Fri, Aug 28, 2009 at 03:22:55PM +0200, Carlo Hamalainen wrote: > I was wondering if there are any Sage related events in Europe later this > year? > > I need to use up my travel funding for this year :) As far as I know, nothing before march 2010 in Marseille. Cheers,

[sage-devel] Re: Forward #sage-support to #sage-devel

Yup, a channel op can set this up pretty easily: http://freenode.net/policy.shtml#channelforwarding On Sep 1, 10:49 am, Jason Grout wrote: > Ahmed Fasih wrote: > > buntfalke made a good suggestion yesterday and I bring it to your > > attention: can we merge the #sage-devel and #sage-support cha

[sage-devel] Re: Forward #sage-support to #sage-devel

Ahmed Fasih wrote: > buntfalke made a good suggestion yesterday and I bring it to your > attention: can we merge the #sage-devel and #sage-support channels by > forwarding all connections to #sage-support to #sage-devel? > Is this even possible for us to do? We don't control the chat servers.

[sage-devel] Forward #sage-support to #sage-devel

buntfalke made a good suggestion yesterday and I bring it to your attention: can we merge the #sage-devel and #sage-support channels by forwarding all connections to #sage-support to #sage-devel? I benefited a lot from #sage-support when I was starting out last year, and usually I tell visitors t

[sage-devel] Re: How do I apply a patch or clean up a repository?

John Cremona wrote: > You may need to recompile from scratch. I would *never* apply a patch > to the mai nbranch, for this reason! > > The reason the hg qimport failed is probably because i nyour .hgrc > file you need to alert hg to the fact that you will be using wueues. > Mine looks like this:

[sage-devel] Re: What units should process size & memory be returned in?

2009/9/1 gsw : > > Hi Dave, > > I'd propose to use ISO C99 notation from "Stdint.h", e.g. "uint64_t", > and do the count in bytes. > This standard notation is even usable on Windows. > (See also http://en.wikipedia.org/wiki/Stdint.h) > > Cheers, > Georg But do we want to rely on an ISO c99 standa

[sage-devel] Sage-4.1.1 test fails for r-2.6.1.p23

Hi, I am trying to compile sage 4.1.1 on my desktop: P4, 2.66GHz, 2.25GB ram Machine: Linux linux-hl2a 2.6.25.20-0.5-pae #1 SMP 2009-08-14 01:48:11 +0200 i686 i686 i386 GNU/Linux gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) I set the environment variable

[sage-devel] Re: What units should process size & memory be returned in?

Hi Dave, I'd propose to use ISO C99 notation from "Stdint.h", e.g. "uint64_t", and do the count in bytes. This standard notation is even usable on Windows. (See also http://en.wikipedia.org/wiki/Stdint.h) Cheers, Georg --~--~-~--~~~---~--~~ To post to this group,

[sage-devel] Re: How do I apply a patch or clean up a repository?

Thanks, John! Is there a simple step-by-step guide to safely applying patches somewhere? Everyone seems to do it differently. I found the following thread helpful, but it would be good to summarise it somewhere: http://groups.google.com/group/sage-devel/browse_thread/thread/6f9b59faccaafc12/300

[sage-devel] Re: How do I apply a patch or clean up a repository?

OK, thanks! It's a mystery to me how people manage to do upgrade after upgrade without running into problems. So far, I have always ended up recompiling from source, earlier or later. Maybe the problems are caused by moving the sage install directory after upgrading. I don't know. Anyway, than

[sage-devel] Re: How do I apply a patch or clean up a repository?

You may need to recompile from scratch. I would *never* apply a patch to the mai nbranch, for this reason! The reason the hg qimport failed is probably because i nyour .hgrc file you need to alert hg to the fact that you will be using wueues. Mine looks like this: [ui] username = John Cremona

[sage-devel] Re: How do I apply a patch or clean up a repository?

On Tue, Sep 1, 2009 at 8:03 AM, Stan Schymanski wrote: > > Hi David, > > Thanks for your help. Yes, I did sage -clone myclone, which returned an > error message, so I changed back to main (sage -b main), started sage, > tried to apply the same patch in main without success and then I thought > I s

[sage-devel] Re: How do I apply a patch or clean up a repository?

Hi David, Thanks for your help. Yes, I did sage -clone myclone, which returned an error message, so I changed back to main (sage -b main), started sage, tried to apply the same patch in main without success and then I thought I should revert to the original by typing hg_sage.revert('--all') -

[sage-devel] What units should process size & memory be returned in?

'top' is being used to determine the memory usage of a process in parts of Sage. I believe this is inappropriate and is causing hassles on Solaris. Robert Bradsure suggested returning the value in bytes with a system call. Robert, or perhaps someone else, said to return the data as a long. I c

[sage-devel] Re: Anyone want an account on first release of Solaris 10 ?

On Mon, Aug 31, 2009 at 11:11 PM, maha a wrote: > Hi , > I love to work with all software that help us in teaching mathematics > using Technology for students in our schools, > I works as a trainer for geogebra program in our schooles , give the > teachers training for interactive mathematics

Re: [codenode-devel] Re: [sage-devel] Re: grant proposal season

On Tue, Sep 1, 2009 at 8:50 PM, Dr. David Kirkby wrote: > > Ondrej Certik wrote: > >> Another idea is something like wolfram alpha: >> it's on my todo to do something like "sympy gamma". And then something >> for femhub (femhub.org) and PDEs, so this could be used with Sage too. > > I think that i

Re: [codenode-devel] Re: [sage-devel] Re: grant proposal season

Ondrej Certik wrote: > Another idea is something like wolfram alpha: > > http://www.wolframalpha.com/ > > it's on my todo to do something like "sympy gamma". And then something > for femhub (femhub.org) and PDEs, so this could be used with Sage too. > Besides being a cool thing (I really like w

[sage-devel] Re: How do I apply a patch or clean up a repository?

On Tue, Sep 1, 2009 at 6:03 AM, Stan Schymanski wrote: > > Dear all, > ... > > I tried different ways of applying a patch with the only success that > I probably made a bit of a > mess in my repository. Is there a way to revert it back to a clean > 4.1.1 > install? I'm not sure what you did to cr

[sage-devel] How do I apply a patch or clean up a repository?

Dear all, Sorry if you see this twice, but my original message does not show up for me, so I am posting it again under a new subject. I tried different ways of applying a patch with the only success that I probably made a bit of a mess in my repository. Is there a way to revert it back to a clea

[sage-devel] Re: Programs in Sage using SCons are really screwed up.

2009/8/31 Bill Hart : > > SCons is much newer than the ancient GNU autotools. It is quite > possible that various subtleties are yet to be sort out in SCons. It > may well be worth reporting this issue to the SCons people, as they > may well not know about it (or may be able to give advice on how

[sage-devel] Re: Sage 4.1.1 build error

Hi, I too ran into this trouble. Fortunately i remembered that including some headers might solve the problem. So in $SAGE_ROOT/spkg/ build/quaddouble-2.2.p9/src/tests/qd_test.cpp i had to add: #include #include I also had to add: #include in $SAGE_ROOT/spkg/build/quaddouble-2.2.p9/src/te

[sage-devel] Re: Sage 4.1.1 build error

On Aug 30, 2009, at 9:07 PM, M. Badawy wrote: > > Hi...I was trying to build from source on Xubuntu 9.04 32bit running > on an IBM Thinkpad T43 w/ Centrino 1.86Ghz proc., 1.5GB Ram. I had to > compile because the version in the repos is just too old (3.0.5), and > the available > binary for 4.1.1

[sage-devel] Re: MPIR build failure on first release of Solaris 10 (03/2005)

As I already told David via email, I can confirm that the Boehm-Weiser garbage collector, the GMP library and ECL itself build using patch 123647-02 (6th March 2008) on top of the first release of Solaris 10. This patch is the first one that makes GCC use Solaris' assembler. Without it, GCC fails

[sage-devel] Re: Inequalities in InfinitePolynomialRing

Hi! On Sep 1, 8:31 am, Nathann Cohen wrote: > Could you tell me why there does not seem to be any support for inequalities > in InfinitePolynomialRing ? Because what you call "inequalities" are symbolic expressions. InfinitePolynomialRing has nothing to do with symbolics. It is about some very

[sage-devel] codenode 0.1 has been released!

Hi all, codenode 0.1 has been released. The major non-code change is that codenode is now licensed under the BSD. We decided on this change because we want codenode to be accessible to a larger range of communities, especially the Scipy/Numpy/Sympy/Matplotlib communities. For recent code chan

Re: [codenode-devel] Re: [sage-devel] Re: Is there any particular reason why Notebook uses Twisted.Web2 instead of Twisted.Web?

On Aug 31, 2009, at 1:32 PM, Alex Clemesha wrote: > On Mon, Aug 31, 2009 at 8:59 AM, William Stein > wrote: >> >> >> On Mon, Aug 31, 2009 at 8:45 AM, Thierry Dumont > lyon1.fr> >> wrote: >>> >>> William Stein a écrit : The first thing I plan to do is consider switching from twi

[sage-devel] Inequalities in InfinitePolynomialRing

Hello everybody Could you tell me why there does not seem to be any support for inequalities in InfinitePolynomialRing ? I would like to express general inequalities of the form x[1] + x[2] < x[3], but each time I evaluate it I get a boolean, which is not quite what I would like to keep of t