[sage-devel] Re: Ports to FreeBSD and/or NetBSD
On Thu, Jun 25, 2009 at 5:49 AM, Robert Bradshaw wrote: > > On Jun 23, 2009, at 4:56 PM, Dr. David Kirkby wrote: > >> >> From the top README.txt >> >> --- >> NOT SUPPORTED: >> * FreeBSD >> * Arch Linux >> * Gentoo Linux >> * Microsoft Windows (via Visual Studio C++) >> * Microsoft Windows (via Cygwin) >> >> We like all of the above operating systems, but just haven't had >> the time to make Sage work well on them. Help wanted! >> --- >> >> Would it not be sensible to ask around on some FreeBSD/NetBSD mailing >> lists etc, and see if one could drum up enough support to start a >> port? >> >> I don't know much about the *BSD's, having never played with them for >> more than a few minutes, but I can't see why there should be any huge >> hurdles to overcome. >> >> Having a port to those would be one big plus over the >> Mathematica/MATLAB/Maple guys. >> >> Typing FreeBSD into Google I get 20 million hits. For NetBSD it is 7.9 >> million. For Solaris it is 40 million, but of course there is the film >> 'Solaris' and some other users. But the *BSDs seem popular enough to >> warrant at least some effort in getting a port started. > > I'm fairly ignorant about porting, but I think the fact that we > already support OS X (very well) should be interesting to anyone > trying to port to some of the other BSDs. The main problems with building Sage on BSD, in my experience, are that (1) you have to "gmake" instead of "make" to run the GNU version of Make, which is a pain, (2) similar problems to (1) with other GNU tools and GNU-isms in Sage, (3) it is hard to install Fortran. In hopes of attracting Dan Bernstein as a user, I used to regularly build and test Sage on BSD for a long time, but for about two years there was not a single Sage user that actually used BSD, so I stopped. When I was going to start again, I installed some BSD's into vmware machines on boxen.math, but could not install Fortran, so I gave up (the official install procedure just segfaulted in all cases when installing fortran for me). It would be useful to have access to a BSD box again, i.e., try again to install BSD and fortran, if we want to support BSD. If we don't have access in our standard build testing workflow, then even if Sage works on BSD, it'll just break again. As far as I know, no freeBSD users have ever offered to give any Sage developers accounts for this purporse yet, so installing our our vmware machine is the best bet. If one searches the Sage mailing lists, there is at least one person who I think has posted a number of fixes he needed to build Sage on BSD, some of which mabshoff put into Sage, and some of which he maybe didn't. Wiliam > >> I do know one very tech-savy FreeBSD guy who is a 'time-nut' but would >> no doubt know the places to ask. If you have never come across the >> 'time-nuts', take a look at this for a very accurate wrist atomic >> watch >> which keeps accurate to a few nanoseconds per day, though the battery >> life is a bit on the short side. >> >> http://leapsecond.com/pages/atomic-bill/ >> >> The guy that runs that site (Tom) is a true 'time-nut' and has done >> things like climb mountains with cesium clocks strapped to his >> body. His >> most accurate time-piece is a hydorogen maser. At one point in time >> (excuse the pun), the definition of a second will probably change >> to be >> in terms of oscillations in the hydrogen maser, as it is more stable >> than cesium, in which the second is currently defined. > > Interesting diversion :) > > - Robert > > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
Nick Alexander wrote: >> I think I'm not communicating my point very clearly. I'm suggesting >> that the release manager have in his patch application script an >> automated "prepend 'Trac #: ' to the commit message" step. > > I thought of implementing this but couldn't think of a way to discover > if there was a ticket number already there! (If you can do that, you > can just use it :) How do you prevent Trac #6346: fix trac #6346? I think it's fine to have two mentions of the ticket number. The first is understood to be automated and corresponds to the actual ticket number the patch was pulled from (so is guaranteed to be correct). In fact, your example shows how commit messages might change: if you know the trac number will go on automatically, then you might give a more descriptive commit message :). Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Ports to FreeBSD and/or NetBSD
On 2009-Jun-24 00:56:38 +0100, "Dr. David Kirkby" wrote: >Would it not be sensible to ask around on some FreeBSD/NetBSD mailing >lists etc, and see if one could drum up enough support to start a port? I've done some work on getting Sage to work on FreeBSD but there is still a way to go. For various reasons, I haven't tried building Sage 4.x yet. It's not clear whether Sage will ever be accepted into the FreeBSD ports system (because the "everything in one tarball" approach used by Sage is inconsistent with the FreeBSD model). See http://wiki.sagemath.org/freebsd for progress to date. >I don't know much about the *BSD's, having never played with them for >more than a few minutes, but I can't see why there should be any huge >hurdles to overcome. Some of the spkg files and underlying applications have "all the world is Linux" assumptions embedded in them - '/bin/sh' being bash and 'make' being GNU make being the most pervasive. I have fixes for most of these (and the Solaris port will run into similar problems). >'Solaris' and some other users. But the *BSDs seem popular enough to >warrant at least some effort in getting a port started. Note that it's not just getting a port started but also having the critical mass to keep the port working. Sage is currently evolving extremely rapidly and so there will be ongoing effort to ensure that Sage remains functional. -- Peter Jeremy pgphQ8JThHW9a.pgp Description: PGP signature
[sage-devel] Re: Ports to FreeBSD and/or NetBSD
On Thu, Jun 25, 2009 at 9:17 AM, wrote: > On 2009-Jun-24 00:56:38 +0100, "Dr. David Kirkby" > wrote: >>Would it not be sensible to ask around on some FreeBSD/NetBSD mailing >>lists etc, and see if one could drum up enough support to start a port? > > I've done some work on getting Sage to work on FreeBSD but there is > still a way to go. For various reasons, I haven't tried building Sage > 4.x yet. It's not clear whether Sage will ever be accepted into the > FreeBSD ports system (because the "everything in one tarball" approach > used by Sage is inconsistent with the FreeBSD model). Sage is in Debian, so it could maybe go into FreeBSD. The Sage in Debian is not "everything in one tarball" -- instead Tim Abbott went through and made sure every single spkg in Sage had a corresponding Debian spkg. > See http://wiki.sagemath.org/freebsd for progress to date. Thanks! > >>I don't know much about the *BSD's, having never played with them for >>more than a few minutes, but I can't see why there should be any huge >>hurdles to overcome. > > Some of the spkg files and underlying applications have "all the world > is Linux" assumptions embedded in them - '/bin/sh' being bash and 'make' > being GNU make being the most pervasive. I have fixes for most of these > (and the Solaris port will run into similar problems). > >>'Solaris' and some other users. But the *BSDs seem popular enough to >>warrant at least some effort in getting a port started. > > Note that it's not just getting a port started but also having the > critical mass to keep the port working. Sage is currently evolving > extremely rapidly and so there will be ongoing effort to ensure that > Sage remains functional. > > -- > Peter Jeremy > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
2009/6/25 Jason Grout : > > Robert Miller wrote: > I think the following is a counterexample to "The trac_ prefix does > not bring any useful information." I still think it's not really, and it is just making the name longer, but I don't really care either. >>> I don't see the use for it either, but it's not a huge issue for me. >> >> I should explain my workflow, as I'm probably not the only person >> doing this (e.g. Craig). When I'm managing releases is one thing, but >> in daily practice, I always download patches to my home directory. >> Think about it. Open a terminal, wget a patch, and this is what > > I presume that you're aware that hg qimport also takes http URLs and > automatically downloads a patch and puts it onto the queue? Ever since > Carl showed that to me, I don't think I've downloaded any patch with wget. > I did not know that, which will be useful. What is the canonical recipe for getting the patch's URL? When I try I sometimes find I have downloaded some html thing by mistake. John > Jason > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
On Jun 25, 2009, at 1:37 AM, John Cremona wrote: > 2009/6/25 Jason Grout : >> >> Robert Miller wrote: >> I think the following is a counterexample to "The trac_ prefix >> does >> not bring any useful information." > I still think it's not really, and it is just making the name > longer, > but I don't really care either. I don't see the use for it either, but it's not a huge issue for me. >>> >>> I should explain my workflow, as I'm probably not the only person >>> doing this (e.g. Craig). When I'm managing releases is one thing, >>> but >>> in daily practice, I always download patches to my home directory. >>> Think about it. Open a terminal, wget a patch, and this is what >> >> I presume that you're aware that hg qimport also takes http URLs and >> automatically downloads a patch and puts it onto the queue? Ever >> since >> Carl showed that to me, I don't think I've downloaded any patch >> with wget. >> > > I did not know that, which will be useful. What is the canonical > recipe for getting the patch's URL? When I try I sometimes find I > have downloaded some html thing by mistake. At the bottom of the html view, there's a link entitled "original format" which gives the raw patch. It's the same as the html-view url, but with "attachment" replaced with "raw-attachment." - Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
On Thu, Jun 25, 2009 at 10:48 AM, Robert
Bradshaw wrote:
>
> On Jun 25, 2009, at 1:37 AM, John Cremona wrote:
>
>> 2009/6/25 Jason Grout :
>>>
>>> Robert Miller wrote:
>>> I think the following is a counterexample to "The trac_ prefix
>>> does
>>> not bring any useful information."
>> I still think it's not really, and it is just making the name
>> longer,
>> but I don't really care either.
> I don't see the use for it either, but it's not a huge issue for
> me.
I should explain my workflow, as I'm probably not the only person
doing this (e.g. Craig). When I'm managing releases is one thing,
but
in daily practice, I always download patches to my home directory.
Think about it. Open a terminal, wget a patch, and this is what
>>>
>>> I presume that you're aware that hg qimport also takes http URLs and
>>> automatically downloads a patch and puts it onto the queue? Ever
>>> since
>>> Carl showed that to me, I don't think I've downloaded any patch
>>> with wget.
>>>
>>
>> I did not know that, which will be useful. What is the canonical
>> recipe for getting the patch's URL? When I try I sometimes find I
>> have downloaded some html thing by mistake.
>
> At the bottom of the html view, there's a link entitled "original
> format" which gives the raw patch. It's the same as the html-view
> url, but with "attachment" replaced with "raw-attachment."
>
And it is a major pain to have to find that link every time you apply
a patch, imho. I hate that. It's a design flaw in trac.
That's why I made
sage: hg_sage.apply('any reasonable url into trac')
work...
William
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
William Stein wrote:
> On Thu, Jun 25, 2009 at 10:48 AM, Robert
> Bradshaw wrote:
>> On Jun 25, 2009, at 1:37 AM, John Cremona wrote:
>>
>>> 2009/6/25 Jason Grout :
Robert Miller wrote:
I think the following is a counterexample to "The trac_ prefix
does
not bring any useful information."
>>> I still think it's not really, and it is just making the name
>>> longer,
>>> but I don't really care either.
>> I don't see the use for it either, but it's not a huge issue for
>> me.
> I should explain my workflow, as I'm probably not the only person
> doing this (e.g. Craig). When I'm managing releases is one thing,
> but
> in daily practice, I always download patches to my home directory.
> Think about it. Open a terminal, wget a patch, and this is what
I presume that you're aware that hg qimport also takes http URLs and
automatically downloads a patch and puts it onto the queue? Ever
since
Carl showed that to me, I don't think I've downloaded any patch
with wget.
>>> I did not know that, which will be useful. What is the canonical
>>> recipe for getting the patch's URL? When I try I sometimes find I
>>> have downloaded some html thing by mistake.
>> At the bottom of the html view, there's a link entitled "original
>> format" which gives the raw patch. It's the same as the html-view
>> url, but with "attachment" replaced with "raw-attachment."
>>
>
> And it is a major pain to have to find that link every time you apply
> a patch, imho. I hate that. It's a design flaw in trac.
> That's why I made
> sage: hg_sage.apply('any reasonable url into trac')
> work...
When Mike was experimenting with trac 0.11, he made a plugin or
something that put a "raw" link next to the attachment link, so an
attachment would look like:
trac_3948_description.patch (raw) Apply on top of previous patches
where clicking on trac_... would bring you to the html page, and
clicking on "raw" would give you the raw attachment.
Does anyone (Mike?) know whatever happened to that functionality?
Jason
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage on Wikipedia
William Stein wrote: > >> * Tools for image processing [5] > > yes, in pylab, plus also there is the Python Imagining Library. (PIL) > Also, don't forget openCV (http://code.google.com/p/ctypes-opencv/, for example). There are also a few other references to using openCV with numpy. Not that I've ever used it, though... Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Ports to FreeBSD and/or NetBSD
On 2009-Jun-25 09:09:02 +0200, William Stein wrote: >The main problems with building Sage on BSD, in my experience, are >that (1) you have to "gmake" instead of "make" to run the GNU version >of Make, which is a pain, My approach to this was to symlink gmake to $SAGE_ROOT/local/bin/make since the latter appears before /usr/bin in the $PATH used to build sage. > (2) similar problems to (1) with other GNU >tools and GNU-isms in Sage, Solved with similar symlinks for bash, gcc & gfortran. I also needed to remove a cople of bash'isms from some configure scripts. > (3) it is hard to install Fortran. I didn't have any problem installing fortran from gcc4.3 but actually getting sage to use it and its libraries was a bit trickier. > When I was going to start again, I installed some BSD's into vmware >machines on boxen.math, but could not install Fortran, so I gave up >(the official install procedure just segfaulted in all cases when >installing fortran for me). "cd /usr/ports/lang/gcc43 && make install" worked for me. If it blows up, you could forward the relevant part of the failure to freebsd-ports (or I would be happy to assist if you mail me directly). > As far as I know, no freeBSD >users have ever offered to give any Sage developers accounts for this >purporse yet, so installing our our vmware machine is the best bet. Unfortunately, I'm not really in a position to provide such accounts on my home machines. If/when sage becomes a port, it will gain access to the FreeBSD ports-build cluster (which automatically builds all ports on all supported architectures/releases and provides build logs). Alternatively, you could send a request to freebsd-ports and you might either find a committer willing to run test builds on the cluster or someone willing to provide you with a shell account on their system. -- Peter Jeremy pgpsWsgemihk0.pgp Description: PGP signature
[sage-devel] Re: Ports to FreeBSD and/or NetBSD
On Thu, Jun 25, 2009 at 11:53 AM, Peter Jeremy wrote: > On 2009-Jun-25 09:09:02 +0200, William Stein wrote: >>The main problems with building Sage on BSD, in my experience, are >>that (1) you have to "gmake" instead of "make" to run the GNU version >>of Make, which is a pain, > > My approach to this was to symlink gmake to $SAGE_ROOT/local/bin/make > since the latter appears before /usr/bin in the $PATH used to build > sage. > >> (2) similar problems to (1) with other GNU >>tools and GNU-isms in Sage, > > Solved with similar symlinks for bash, gcc & gfortran. I also needed > to remove a cople of bash'isms from some configure scripts. > >> (3) it is hard to install Fortran. > > I didn't have any problem installing fortran from gcc4.3 but actually > getting sage to use it and its libraries was a bit trickier. > >> When I was going to start again, I installed some BSD's into vmware >>machines on boxen.math, but could not install Fortran, so I gave up >>(the official install procedure just segfaulted in all cases when >>installing fortran for me). > > "cd /usr/ports/lang/gcc43 && make install" worked for me. If it blows > up, you could forward the relevant part of the failure to freebsd-ports > (or I would be happy to assist if you mail me directly). I'll make you an account on the machine and give you root privileges. What login name do you want (email me offlist)? Also, do you prefer 32 or 64-bit for working on this port? I think we should push through the port with your help and get all of your fixes into Sage ASAP. Step 1 is getting this shared BSD resource going and working. -- William > >> As far as I know, no freeBSD >>users have ever offered to give any Sage developers accounts for this >>purporse yet, so installing our our vmware machine is the best bet. > > Unfortunately, I'm not really in a position to provide such accounts > on my home machines. If/when sage becomes a port, it will gain access > to the FreeBSD ports-build cluster (which automatically builds all > ports on all supported architectures/releases and provides build logs). > Alternatively, you could send a request to freebsd-ports and you might > either find a committer willing to run test builds on the cluster or > someone willing to provide you with a shell account on their system. > > -- > Peter Jeremy > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage on Wikipedia
Simon King wrote: > Hi > > On Jun 24, 8:33 pm, kcrisman wrote: >> A related page to look at would >> behttp://en.wikipedia.org/wiki/Comparison_of_computer_algebra_systems I updated that somewhat, expanded the description similar to that for Mathematica. I removed the 'Boolean Computation' which Mathematica does, and added the fact it's GUI was web based. I spent some time yesterday adding Sage to these pages, as it did not even exist on them. In the case of the stats package, I just selected 'yes' to anything R had. http://en.wikipedia.org/wiki/Comparison_of_numerical_analysis_software http://en.wikipedia.org/wiki/Comparison_of_statistical_packages > It is stated on that page that Sage does not support Unix. Is that > really the case? > > Also it is stated that it does not support Windows. Well, not > natively, but it does via vmware. > > Cheers, > Simon Unix is tricky, as Solaris works, on some machines, but is not fully supported. (To be precise about this, one needs a definition of 'support'). I think on Wikipedia, the 'ports' sections indicates if it runs natively, so Windows should remain a 'no'. There is no harm though it adding a footnote and a link to some details about using VMware. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Custom definitions for latex style
Dear all,
I have been asked to forward the below to the sage-devel list. Ticket
#6290 introduced a way to custom-define the latex style of functions,
but it would be great if something similar was made possible for any
variable. Is there a way for this already? I used to do it in the
following way, but now I get an error message:
sage: var('hi kunsati delyui')
sage: hi._latex_ = lambda: 'h_i' # Matric suction
head in layer i (=pcapvec)
sage: kunsati._latex_ = lambda: 'K_{unsat,i}' # Unsaturated
hydraulic conductivity in layer i
sage: delyui._latex_ = lambda: '\delta_{yu,i}'# Soil layer
thickness in layer i
Traceback (most recent call last):
...
AttributeError: 'sage.symbolic.expression.Expression' object attribute
'_latex_' is read-only
I already posted this to sage-support, so sorry for any cross-posting.
Cheers,
Stan
Original Message
Subject:Re: [Sage] #6290: [with patch, positive review] Allow keywords
such as latex_name=LaTeX while defining symbolic function
Date: Thu, 25 Jun 2009 10:44:11 -
From: Sage
Reply-To: wst...@math.washington.edu
CC: sage-t...@googlegroups.com
References: <041.15719bbafe146f47dcdcaf3a09ccf...@math.washington.edu>
#6290: [with patch, positive review] Allow keywords such as latex_name=LaTeX
while
defining symbolic function
---+
Reporter: gmhossain |Owner:
Type: enhancement| Status: closed
Priority: major |Milestone: sage-4.1
Component: symbolics | Resolution: fixed
Keywords: latex_name, symbolic function | Reviewer: Nick Alexander
Author: Golam Mortuza Hossain | Merged: 4.1.alpha0
---+
Comment(by gmhossain):
Replying to [comment:8 schymans]:
> Would something similar be possible whenever a variable is defined?
> E.g. if I want to use multiple subscripts, I would like to define
> var('A_gs', latex_name="A_{gs}").
Hmmm, thats a great suggestion. Could you please post this to sage-devel?
--
Ticket URL:
Sage
[sage-devel] Re: Custom definitions for latex style
On Thu, 25 Jun 2009 13:22:46 +0200
Stan Schymanski wrote:
>
> Dear all,
>
> I have been asked to forward the below to the sage-devel list. Ticket
> #6290 introduced a way to custom-define the latex style of functions,
> but it would be great if something similar was made possible for any
> variable. Is there a way for this already? I used to do it in the
> following way, but now I get an error message:
>
> sage: var('hi kunsati delyui')
> sage: hi._latex_ = lambda: 'h_i' # Matric suction
> head in layer i (=pcapvec)
> sage: kunsati._latex_ = lambda: 'K_{unsat,i}' # Unsaturated
> hydraulic conductivity in layer i
> sage: delyui._latex_ = lambda: '\delta_{yu,i}'# Soil layer
> thickness in layer i
> Traceback (most recent call last):
> ...
> AttributeError: 'sage.symbolic.expression.Expression' object attribute
> '_latex_' is read-only
Since Expression is a cython class, you cannot overwrite the _latex_()
method.
Pynac supports setting latex names for variables at creation, but this
functionality is not exposed in the wrapper. Another solution by
hacking latex_variable_name() might be possible, but I would like to
avoid that if possible.
Feel free to open a new issue in trac about it.
Cheers,
Burcin
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
Build failed for intel macbook 10.4.11 Should I post the full log somewhere? Here is the tail: /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3-i386-2.5/sage/misc/darwin_memory_usage.o -w sage/misc/darwin_memory_usage.c:7:32: error: mach/shared_region.h: No such file or directory sage/misc/darwin_memory_usage.c: In function ‘shared_region_size’: sage/misc/darwin_memory_usage.c:34: error: ‘SHARED_REGION_SIZE_PPC’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:34: error: (Each undeclared identifier is reported only once sage/misc/darwin_memory_usage.c:34: error: for each function it appears in.) sage/misc/darwin_memory_usage.c:36: error: ‘SHARED_REGION_SIZE_PPC64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:38: error: ‘SHARED_REGION_SIZE_I386’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:40: error: ‘SHARED_REGION_SIZE_X86_64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c: In function ‘in_shared_region’: sage/misc/darwin_memory_usage.c:48: error: ‘SHARED_REGION_BASE_PPC’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:49: error: ‘SHARED_REGION_SIZE_PPC’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:54: error: ‘SHARED_REGION_BASE_PPC64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:55: error: ‘SHARED_REGION_SIZE_PPC64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:60: error: ‘SHARED_REGION_BASE_I386’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:61: error: ‘SHARED_REGION_SIZE_I386’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:66: error: ‘SHARED_REGION_BASE_X86_64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:67: error: ‘SHARED_REGION_SIZE_X86_64’ undeclared (first use in this function) error: command 'gcc' failed with exit status 1 sage: There was an error installing modified sage library code. On Wed, Jun 24, 2009 at 8:04 AM, Robert Miller wrote: > > This is the first release of the new cycle, and I've agreed to step in > and co-chair the release with Tom. The source tarball and sage.math > binary are available: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0.tar > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0-sage.math-only-x86_64-Linux.tar.gz > > This is the first development release in which the new merge tools > were used by people other than the authors. Several doctests fail on > sage.math: > >sage -t devel/sage-main/sage/graphs/graph.py # 25 doctests > failed >sage -t devel/sage-main/sage/databases/database.py # 20 > doctests failed >sage -t devel/sage-main/sage/geometry/polyhedra.py # 1 > doctests failed > > These are all due to the removal of graph_isom.pyx, and I will be > posting a patch to fix this shortly, at #6394. I think that there was > no way to avoid these failures, since the only way to expose them was > to remove the code, rebuild entirely from scratch, and then run the > tests. > > This release does not include any tickets involving spkg's. I will > make this the main focus of alpha1, which should drop before Friday. > > Each of the following tickets were rejected by the merge scripts, but > unfortunately the failures are not available at this time (this is due > to human error on my part). If you are involved with one of them, you > are encouraged to try applying the patches to 4.1.alpha0 and see why/ > if they failed. Tom and I will eventually do this, but it would be > helpful for people involved in the ticket to get things started: > > 6196 > 5481 > 6276 > 4712 > 5517 > 5991 > 6164 > 6200 > 5902 > 6269 > > Other easy ways to save release managers time, resulting in more > frequent releases and shorter wait times to get your code merged: > > * Please include the trac number in each commit message if possible. > * Please make sure Author and Reviewer fields are set, when changing > the ticket status to "positive review." Since these are used in > generating release notes, please use full names. > * Please adhere to the "trac_-description.patch" filename format > when creating patch files. > > Cheers, > > Robert Miller (and Tom Boothby) > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage on Wikipedia
On Thu, Jun 25, 2009 at 1:06 PM, Dr. David Kirkby wrote: > > Simon King wrote: >> Hi >> >> On Jun 24, 8:33 pm, kcrisman wrote: >>> A related page to look at would >>> behttp://en.wikipedia.org/wiki/Comparison_of_computer_algebra_systems > > I updated that somewhat, expanded the description similar to that for > Mathematica. I removed the 'Boolean Computation' which Mathematica does, > and added the fact it's GUI was web based. > > I spent some time yesterday adding Sage to these pages, as it did not > even exist on them. In the case of the stats package, I just selected > 'yes' to anything R had. > > http://en.wikipedia.org/wiki/Comparison_of_numerical_analysis_software > http://en.wikipedia.org/wiki/Comparison_of_statistical_packages > >> It is stated on that page that Sage does not support Unix. Is that >> really the case? >> >> Also it is stated that it does not support Windows. Well, not >> natively, but it does via vmware. >> >> Cheers, >> Simon > > Unix is tricky, as Solaris works, on some machines, but is not fully > supported. (To be precise about this, one needs a definition of 'support'). Sage works on OS X, and OS X has been officially certified to be "UNIX". http://arstechnica.com/apple/news/2007/08/mac-os-x-leopard-receives-unix-03-certification.ars > I think on Wikipedia, the 'ports' sections indicates if it runs > natively, so Windows should remain a 'no'. There is no harm though it > adding a footnote and a link to some details about using VMware. Sounds good. William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Custom definitions for latex style
Thanks for the quick reply. This is now Ticket #6403. How much effort
would it be to expose this Pynac functionality?
Cheers,
Stan
Burcin Erocal wrote:
> On Thu, 25 Jun 2009 13:22:46 +0200
> Stan Schymanski wrote:
>
>
>> Dear all,
>>
>> I have been asked to forward the below to the sage-devel list. Ticket
>> #6290 introduced a way to custom-define the latex style of functions,
>> but it would be great if something similar was made possible for any
>> variable. Is there a way for this already? I used to do it in the
>> following way, but now I get an error message:
>>
>> sage: var('hi kunsati delyui')
>> sage: hi._latex_ = lambda: 'h_i' # Matric suction
>> head in layer i (=pcapvec)
>> sage: kunsati._latex_ = lambda: 'K_{unsat,i}' # Unsaturated
>> hydraulic conductivity in layer i
>> sage: delyui._latex_ = lambda: '\delta_{yu,i}'# Soil layer
>> thickness in layer i
>> Traceback (most recent call last):
>> ...
>> AttributeError: 'sage.symbolic.expression.Expression' object attribute
>> '_latex_' is read-only
>>
>
> Since Expression is a cython class, you cannot overwrite the _latex_()
> method.
>
> Pynac supports setting latex names for variables at creation, but this
> functionality is not exposed in the wrapper. Another solution by
> hacking latex_variable_name() might be possible, but I would like to
> avoid that if possible.
>
> Feel free to open a new issue in trac about it.
>
>
> Cheers,
> Burcin
>
>
> >
>
--
Stan Schymanski
Scientist
Max Planck Institute for Biogeochemistry
Postfach 10 01 64
D-07701 Jena
Phone: +49.3641.576264
Fax: +49.3641.577274
WWW: http://www.bgc-jena.mpg.de/~sschym
Biospheric Theory and Modelling Group
http://www.bgc-jena.mpg.de/bgc-theory/
_
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] bug in assume()?
Dear all, this seems like a bug to me:
--
| Sage Version 4.0.2, Release Date: 2009-06-18 |
| Type notebook() for the GUI, and license() for information.|
--
sage: var('mvg nvg')
(mvg, nvg)
sage: assume(mvg, 'integer')
sage: assume(nvg, 'integer')
---
AttributeErrorTraceback (most recent call
last)
/Users/sschym/ in ()
/Users/sschym/Programs/sage/local/lib/python2.5/site-packages/sage/
symbolic/assumptions.pyc in assume(*args)
194 else:
195 try:
--> 196 x.assume()
197 except KeyError:
198 raise TypeError, "assume not defined for
objects of type '%s'"%type(x)
/Users/sschym/Programs/sage/local/lib/python2.5/site-packages/sage/
symbolic/assumptions.pyc in assume(self)
96 maxima.set("context", cur)
97
---> 98 if not self in _assumptions:
99 maxima.activate(self._context)
100 _assumptions.append(self)
/Users/sschym/Programs/sage/local/lib/python2.5/site-packages/sage/
symbolic/assumptions.pyc in __cmp__(self, other)
70 if isinstance(self, GenericDeclaration) and isinstance
(other, GenericDeclaration):
71 return cmp( (self._var, self._assumption),
---> 72 (other._var, other._assumption) )
73 else:
74 return cmp(type(self), type(other))
/Users/sschym/Programs/sage/local/lib/python2.5/site-packages/sage/
symbolic/expression.so in
sage.symbolic.expression.Expression.__nonzero__ (sage/symbolic/
expression.cpp:7506)()
sage: assumptions()
[mvg is integer]
Why did it work for mvg but not for nvg? This was not a problem in
Sage 3.x.
Cheers,
Stan
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: building sage in parallel in parallel
On Mon, Jun 22, 2009 at 4:29 PM, jyr wrote:
>
> Below is a python script that implements the above and sets
> environment variables for parallel compiles. Just save the script to
> makesage.py (say) in the sage root dir and run it via
>
> python makesage.py -j8
>
> It reduced the sage-4.0.2 compile to 1hour 51 minutes on a dual quad
> AMD 2GHz machine.
Thanks. Any thoughts about how to *fix* the build of Sage so that it works
the first time instead of having to try 3 times. But again, thanks!
>
> --
>
> import os,sys
> import getopt
>
>
> def replace_install(sj):
> fpin=open('spkg/install',"r")
> sinstall=fpin.readlines()
> fpin.close()
>
> for iline,sline in enumerate(sinstall):
> if 'time make' in sline and '-f standard/deps $1' in sline:
> sinstall[iline]='time make '+sj+' -f standard/deps $1\n'
> sinstall="".join(sinstall)
>
> fpou=open('spkg/install',"w")
> fpou.write(sinstall)
> fpou.close()
>
>
> def main(argv):
> sj='-j1'
> try:
> opts,args=getopt.getopt(argv[1:],"j:")
> except getopt.GetoptError:
> #print_usage()
> sys.exit(1)
> for oo,aa in opts:
> if oo in ("-j"):
> sj="-j"+aa
>
> smake='make '+sj
> os.environ['MAKE']=smake
>
> replace_install(sj)
>
> os.system('export MAKE="%s"'%(smake)+' && make')
>
> replace_install(sj)
>
> os.system('export MAKE="%s"'%(smake)+' && make')
>
> replace_install('')
>
> os.system('export MAKE="%s"'%(smake)+' && make')
>
>
>
> if __name__ == '__main__':
> main(sys.argv)
>
> >
>
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
> > Is there an -upgrade location to go to? If the answer is no for the foreseeable future, that's understandable. Just asking! - kcrisman --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
On Thu, 25 Jun 2009 at 09:37AM +0100, John Cremona wrote:
> I did not know that, which will be useful. What is the canonical
> recipe for getting the patch's URL? When I try I sometimes find I
> have downloaded some html thing by mistake.
I didn't know that qimport did that either, so I made this bash
function:
function qimport_sage_patch
{
local HG="hg"
local PATCH=$(echo $1 | sed -e 's|/attachment/|/raw-attachment/|')
$HG qimport $PATCH
}
You can right-click on a patch link in trac, select copy, and then do
"qimport_sage_patch http://";. You can set HG to "sage -hg" or
whatever. Put this in your .bashrc and it'll always be available.
You can also use sage_hg_patch or whatever it was that William
suggested. :)
Dan
--
--- Dan Drake
- KAIST Department of Mathematical Sciences
--- http://mathsci.kaist.ac.kr/~drake
signature.asc
Description: Digital signature
[sage-devel] Re: Sage on Wikipedia
William Stein wrote: >>> Cheers, >>> Simon >> Unix is tricky, as Solaris works, on some machines, but is not fully >> supported. (To be precise about this, one needs a definition of 'support'). > > Sage works on OS X, and OS X has been officially certified to be "UNIX". There is a separate column for OS X, so I assume the 'Unix' bit means some unix other than OS X -i.e. Solaris, HP-UX, AIX, tru64, SCO, etc. I've not looked around to find out exactly what is meant there I must admit. > http://arstechnica.com/apple/news/2007/08/mac-os-x-leopard-receives-unix-03-certification.ars > >> I think on Wikipedia, the 'ports' sections indicates if it runs >> natively, so Windows should remain a 'no'. There is no harm though it >> adding a footnote and a link to some details about using VMware. > > Sounds good. > > William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: typesetting partial derivatives
Hi Burcin,
On Wed, Jun 24, 2009 at 6:54 PM, Burcin Erocal wrote:
> I attached a patch to the trac ticket that contains an initial attempt
> at the MMA notation:
>
> http://trac.sagemath.org/sage_trac/ticket/6344
>
>
> It doesn't work well for text mode:
>
> sage: f = function('f')
> sage: f(x).derivative(x,3)
> f^{(3)}(x)
My suggestion would be to split out "text-mode" (repr) output
for another ticket. Current text-mode output expression from Sage
in this case is not a valid input expression of Sage. For example,
if I do copy-n-paste output like "D[0](f)(x)" to another cell then
Sage doesn't recognize it.
I guess, implementing latex output would be easier one. I did
a quick-hack MMA style. It worked fine and with primes
it appears to be in "textbook style".
Cheers,
Golam
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
On Thu, Jun 25, 2009 at 02:19:38AM -0700, Jason Grout wrote:
> >> At the bottom of the html view, there's a link entitled "original
> >> format" which gives the raw patch. It's the same as the html-view
> >> url, but with "attachment" replaced with "raw-attachment."
> >>
> >
> > And it is a major pain to have to find that link every time you apply
> > a patch, imho. I hate that. It's a design flaw in trac.
> > That's why I made
> > sage: hg_sage.apply('any reasonable url into trac')
> > work...
>
> When Mike was experimenting with trac 0.11, he made a plugin or
> something that put a "raw" link next to the attachment link, so an
> attachment would look like:
>
> trac_3948_description.patch (raw) Apply on top of previous patches
>
> where clicking on trac_... would bring you to the html page, and
> clicking on "raw" would give you the raw attachment.
+1 !
Nicolas
--
Nicolas M. Thiéry "Isil"
http://Nicolas.Thiery.name/
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
On 25-Jun-09, at 5:10 AM, David Joyner wrote: > Build failed for intel macbook 10.4.11 > > Should I post the full log somewhere? Here is the tail: > > > /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 > -c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3- > i386-2.5/sage/misc/darwin_memory_usage.o -w > sage/misc/darwin_memory_usage.c:7:32: error: mach/shared_region.h: > No such file or directory I merged this patch and forgot how volatile Mach headers and the like are. Could you use locate or spotlight to find shared_region.h on your machine and tell me where it is? Also, can you give info about your development chain, such as the version of XCode, gcc, etc. Nick --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
On 25 Jun., 14:10, David Joyner wrote: > Build failed for intel macbook 10.4.11 > > Should I post the full log somewhere? Here is the tail: > > /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c > sage/misc/darwin_memory_usage.c -o > build/temp.macosx-10.3-i386-2.5/sage/misc/darwin_memory_usage.o -w > sage/misc/darwin_memory_usage.c:7:32: error: mach/shared_region.h: No such > file or directory > sage/misc/darwin_memory_usage.c: In function ‘shared_region_size’: > sage/misc/darwin_memory_usage.c:34: error: ‘SHARED_REGION_SIZE_PPC’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:34: error: (Each undeclared identifier is > reported only once > sage/misc/darwin_memory_usage.c:34: error: for each function it appears in.) > sage/misc/darwin_memory_usage.c:36: error: ‘SHARED_REGION_SIZE_PPC64’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:38: error: ‘SHARED_REGION_SIZE_I386’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:40: error: ‘SHARED_REGION_SIZE_X86_64’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c: In function ‘in_shared_region’: > sage/misc/darwin_memory_usage.c:48: error: ‘SHARED_REGION_BASE_PPC’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:49: error: ‘SHARED_REGION_SIZE_PPC’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:54: error: ‘SHARED_REGION_BASE_PPC64’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:55: error: ‘SHARED_REGION_SIZE_PPC64’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:60: error: ‘SHARED_REGION_BASE_I386’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:61: error: ‘SHARED_REGION_SIZE_I386’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:66: error: ‘SHARED_REGION_BASE_X86_64’ > undeclared (first use in this function) > sage/misc/darwin_memory_usage.c:67: error: ‘SHARED_REGION_SIZE_X86_64’ > undeclared (first use in this function) > error: command 'gcc' failed with exit status 1 > sage: There was an error installing modified sage library code. > Someone please back out patch #6027, and set it to "needs work". It's clearly is the reason for this brokenness, and wasn't tested on Mac OS X 10.4 at all. As it is stated in its comments. Cheers, gsw --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Maxima Errors
Hello I am currently attempting to use sage to research graph polynomials. In particular, I am trying to generate and store the matchings polynomial for as many graphs as is possible. The routines I am employing are simple, and I have used them extensively (computing the matchings polynomial for all graphs on at most 7 vertices). In trying to extend my computations I have run into a number of Maxima errors that I am at a loss to explain. These errors occur only after several thousand consecutive calculations, and fail to repeat themselves when the offending calculation is immediately repeated. I have attached a text file containing the exact error messages. Any suggestions you have would be welcome. Thanks in advance, Brendan Rooney --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~--- Error the first: Traceback (most recent call last): output.close() File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 2885, in coefficients S = symbolic_expression_from_maxima_string(repr(G)) File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 9029, in symbolic_expression_from_maxima_string raise TypeError, "unable to make sense of Maxima expression '%s' in Sage"%s TypeError: unable to make sense of Maxima expression '"__SAGE_SYNCHRO_MARKER_212074193"' in Sage This error arose while trying to compute the matchings polynomial for all graphs on 8 vertices. The solution was simply to break the list into lists with at most 1000 elements. Error the second: Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Traceback (most recent call last): print 'finished '+str(i)+' out of '+str(len(Q)) File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 2886, in coefficients return S[1:] TypeError: 'SymbolicFunctionEvaluation' object is unsubscriptable This error arose while trying to calculate the matchings polynomial for all graphs on 9 vertices. I broke the list into sublists of size 1000, but still ended up with an error after several hours of computation. Interesting side note: Maxima crashes predictably after between 5000 and 6000 computations. Error the third: Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Traceback (most recent call last): input.close() File "/usr/local/bin/sage/local/lib/python2.5/site-packages/SQLAlchemy-0.4.6-py2.5.egg/", line 11, in File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 2884, in coefficients G = f.coeffs(x) File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/interfaces/expect.py", line 1466, in __getattr__ P = self._check_valid() File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/interfaces/expect.py", line 1419, in _check_valid raise ValueError, "The %s session in which this object was defined is no longer running."%P.name() ValueError: The maxima session in which this object was defined is no longer running. This error arose while trying to calculate the matchings polynomial for all graphs on 9 vertices. It occured even after storing the input strings in small files, and processing them individually. Error the fourth: Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Maxima crashed -- automatically restarting. Traceback (most recent call last): File "", line 1, in File "/home/spaceman/.sage/sage_notebook/worksheets/admin/9/code/231.py", line 11, in if Qd[i][key](_sage_const_1 ) == _sage_const_0 : File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 4819, in __call__ new_ops.append( op(*[args[i] for i in indices]) ) File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 4819, in __call__ new_ops.append( op(*[args[i] for i in indices]) ) File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 4807, in __call__ op_vars = op.variables() File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 4622, in variables return self.simplify().variables() File "/usr/local/bin/sage/local/lib/python2.5/s
[sage-devel] Re: Maxima Errors
Hi Brendan, On Thu, 25 Jun 2009 11:58:59 -0400 Brendan Rooney wrote: > Hello > > I am currently attempting to use sage to research graph polynomials. > In particular, I am trying to generate and store the matchings > polynomial for as many graphs as is possible. The routines I am > employing are simple, and I have used them extensively (computing the > matchings polynomial for all graphs on at most 7 vertices). > > In trying to extend my computations I have run into a number of > Maxima errors that I am at a loss to explain. These errors occur only > after several thousand consecutive calculations, and fail to repeat > themselves when the offending calculation is immediately repeated. I > have attached a text file containing the exact error messages. Any > suggestions you have would be welcome. Which version of Sage are you using? The error file attached to your previous messsage contains this: Traceback (most recent call last): print 'finished '+str(i)+' out of '+str(len(Q)) File "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", line 2886, in coefficients return S[1:] TypeError: 'SymbolicFunctionEvaluation' object is unsubscriptable SymbolicFunctionEvaluation doesn't exist since Sage-4.0. Cheers, Burcin --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
Sorry, I forgot to post a location. I will for alpha1, which will drop shortly. On Jun 25, 3:39 pm, kcrisman wrote: > > Is there an -upgrade location to go to? > > If the answer is no for the foreseeable future, that's > understandable. Just asking! > > - kcrisman --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
> Someone please back out patch #6027, and set it to "needs work". > > It's clearly is the reason for this brokenness, and wasn't tested on > Mac OS X 10.4 at all. As it is stated in its comments. William is working on this right now, and will post a patch momentarily. rlm --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
Jason Grout wrote: > When Mike was experimenting with trac 0.11, he made a plugin or > something that put a "raw" link next to the attachment link, so an > attachment would look like: > > trac_3948_description.patch (raw) Apply on top of previous patches > > where clicking on trac_... would bring you to the html page, and > clicking on "raw" would give you the raw attachment. > > Does anyone (Mike?) know whatever happened to that functionality? I found http://trac.edgewall.org/ticket/5718 but I'm not sure if the changes are easy to backport. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Sage-4.1.alpha1
This release is primarily the Python upgrade. The source tarball and sage.math binary are here: http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.tar.gz If you care to try upgrading (do so at your own risk -- upgrading has been seen to not work, but not seen to work), the bits are here: http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ I owe much gratitude to Mike Hansen, Martin Albrecht and particularly William Stein for help with getting the Python upgrade to work. These are the known doctest failures: sage -t -long devel/sage/sage/modules/ vector_real_double_dense.pyx # 1 doctests failed sage -t -long devel/sage/doc/fr/tutorial/programming.rst # 1 doctests failed I haven't looked into these, since I have spent about eleven hours out of the last thirty on the Python upgrade. Tom Boothby will take over for alpha2, and I will merge more spkg's for alpha3, which will also be rc0. Cheers, Robert Miller --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
Hi folks, On Fri, Jun 26, 2009 at 4:18 AM, Robert Miller wrote: > > This release is primarily the Python upgrade. The following tickets were merged in Sage 4.1.alpha1: #6085: Robert Miller: Finish full implementation of c_graphs [Reviewed by Tom Boothby] #6359: Mike Hansen: update to Python 2.6.2 [Reviewed by Robert Miller] #6394: Robert Miller: Fix fallout from removal of graph_isom in 4.1.alpha1 [Reviewed by Tom Boothby] -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
On Thu, Jun 25, 2009 at 11:41 AM, Nick Alexander wrote: > > > On 25-Jun-09, at 5:10 AM, David Joyner wrote: > >> Build failed for intel macbook 10.4.11 >> >> Should I post the full log somewhere? Here is the tail: >> >> >> /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 >> -c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3- >> i386-2.5/sage/misc/darwin_memory_usage.o -w >> sage/misc/darwin_memory_usage.c:7:32: error: mach/shared_region.h: >> No such file or directory > > I merged this patch and forgot how volatile Mach headers and the like > are. Could you use locate or spotlight to find shared_region.h on > your machine and tell me where it is? Also, can you give info about It doesn't seem to exist. (I also tried similar names but no dice.) > your development chain, such as the version of XCode, gcc, etc. i686-apple-darwin8-gcc-4.0.1 Looks like I have XDarwin 1.4a1. Does that help? > > Nick > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: video for sage days 16
Hi, On Tue, Jun 23, 2009 at 11:50 PM, William Stein wrote: > > Hi, > > Video and slides for *all* the talks so far from Sage Days 16 are now > posted here: > > http://wiki.sagemath.org/days16 I have embedded the first two videos here: http://sage.math.washington.edu/home/ondrej/scratch/sd16/videos.html let me know if it works for you in your browser. To save bandwidth, I have set the above page *not* to start playing automatically (neither to start automatically buffer the video), so you have to click on the video to start playing (and buffering). This can be trivially changed in the html source code. That page also contains a link to the code + info how to embed such videos. I am experimenting with that, since youtube only allows ~10 minutes, vimeo allows more, but restrict to 1 high definition video upload per week. Here I am hosting the video files on the sage.math server and that's it, no restrictions. Well, except that I had to convert those mp4 files to FLV using mencoder (script for doing so is available on the page above), which might have lost some quality, it was saying "Skipping frame!" almost all the time on my laptop while converting the video, so I guess it has some skipped frames, but it looks quite ok to me. If you figure out how to convert the videos to FLV in some better way, let me know! Ondrej --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Maxima Errors
Perhaps your computation required more space than was available in the Lisp system that was running your version of Maxima. You might, for example, run out of "string" space on some Lisp systems, without totally using up all storage. Since you do not give enough information to reproduce your problem in Maxima (nor do you even address the issue of which version of Maxima you are using) it is pretty hard to help from the Maxima perspective. If you want help in Maxima, I suggest you construct a file of Maxima commands that will do your computation, and run it in Maxima (perhaps a better version than the one packaged with Sage) and see what happens. RJF On Jun 25, 9:14 am, Burcin Erocal wrote: > Hi Brendan, > > On Thu, 25 Jun 2009 11:58:59 -0400 > > Brendan Rooney wrote: > > Hello > > > I am currently attempting to use sage to research graph polynomials. > > In particular, I am trying to generate and store the matchings > > polynomial for as many graphs as is possible. The routines I am > > employing are simple, and I have used them extensively (computing the > > matchings polynomial for all graphs on at most 7 vertices). > > > In trying to extend my computations I have run into a number of > > Maxima errors that I am at a loss to explain. These errors occur only > > after several thousand consecutive calculations, and fail to repeat > > themselves when the offending calculation is immediately repeated. I > > have attached a text file containing the exact error messages. Any > > suggestions you have would be welcome. > > Which version of Sage are you using? > > The error file attached to your previous messsage contains this: > > Traceback (most recent call last): > print 'finished '+str(i)+' out of '+str(len(Q)) > File > "/usr/local/bin/sage/local/lib/python2.5/site-packages/sage/calculus/calculus.py", > line 2886, in coefficients return S[1:] TypeError: > 'SymbolicFunctionEvaluation' object is unsubscriptable > > SymbolicFunctionEvaluation doesn't exist since Sage-4.0. > > Cheers, > Burcin --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
Upgrade from 4.0.2 failed (as predicted by the original poster!) during build of sage.spkg on PPC X.4, with a lot of ImportErrors e.g. no module named mercurial, no module named jinja (to import from). It also pulled the outputs of the documentation, which seemed strange to me (as opposed to building it), e.g. sage-4.1.alpha1/doc/output/html/ en/reference/_sources/sage/rings/laurent_series_ring_element.txt Hope this helps. - kcrisman --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Maxima Errors
Hi, I suspect you're just running out of RAM. Not necessarily physically, but the construction Sage --> expect interface --> Maxima --> Lisp implementation is a fragile one. If the Lisp implementation "thinks" it runs out of space, this is not handled too gracefully by Maxima, and as a consequence the synchronization between Sage/the expect interface, and Maxima, gets lost more or less often. Three options (none, or all, might help): - alter your code to do your computations in "smaller pieces" - move to a "bigger" machine - use a current Sage version (maybe the clisp ---> ecl switch does heal your problem, or the pynac switch, or ...) Good luck! Cheers, gsw --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage on Wikipedia
The link to the sage tutorial from the knol article seems to be broken On Jun 24, 7:19 pm, Harald Schilly wrote: > On Jun 24, 6:16 pm, Robert Bradshaw > wrote: > > > I'll second this. Wikipedia is the highest source of traffic for > > Cython after google and people typing in cython.org directly (despite > > an only average page)--I wouldn't be surprised if it accounts for a > > significant proportion of potential and actual sage hits as well. > > I can give you some numbers, but in general you are right. Don't > forget, there are also other wikipedia language editions that give a > fair amount of traffic, especially french. > > Besides wikipedia, there is also knol, google's version of an > wikipedia for experts. This means, that an article is always > associated with an author and there are no "independent" topics. Last > time when I improved Sage's wikipedia page, I also started > this:http://knol.google.com/k/harald-schilly/sage > It's very general, but improvements are welcome. Anybody is invited to > suggest some improvements or more directly, I can also add others > (with a google account) to become editors. > > H --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
Unfortunately, I don't have access to a OSX <= 10.4 box otherwise I would have ported this code to those versions when I originally wrote the code for this patch. If anyone has a machine available with OSX 10.4 or 10.3 I'd be happy to port this code to it. On Thu, Jun 25, 2009 at 9:47 AM, Robert Miller wrote: > >> Someone please back out patch #6027, and set it to "needs work". >> >> It's clearly is the reason for this brokenness, and wasn't tested on >> Mac OS X 10.4 at all. As it is stated in its comments. > > William is working on this right now, and will post a patch > momentarily. > > rlm > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage on Wikipedia
On Jun 25, 10:39 pm, Utpal Sarkar wrote: > The link to the sage tutorial from the knol article seems to be broken > thx, fixed. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.alpha0
On Thu, Jun 25, 2009 at 9:09 PM, David Joyner wrote: > > On Thu, Jun 25, 2009 at 11:41 AM, Nick Alexander wrote: >> >> >> On 25-Jun-09, at 5:10 AM, David Joyner wrote: >> >>> Build failed for intel macbook 10.4.11 >>> >>> Should I post the full log somewhere? Here is the tail: >>> >>> >>> /Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 >>> -c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3- >>> i386-2.5/sage/misc/darwin_memory_usage.o -w >>> sage/misc/darwin_memory_usage.c:7:32: error: mach/shared_region.h: >>> No such file or directory >> >> I merged this patch and forgot how volatile Mach headers and the like >> are. Could you use locate or spotlight to find shared_region.h on >> your machine and tell me where it is? Also, can you give info about > > It doesn't seem to exist. (I also tried similar names but no dice.) > > >> your development chain, such as the version of XCode, gcc, etc. > > > i686-apple-darwin8-gcc-4.0.1 > > Looks like I have XDarwin 1.4a1. Does that help? > I posted a patch that changes the code so that it isn't used on OS X <= 10.4. That's in sage-4.1.alpha1.tar already... William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
> On Thu, Jun 25, 2009 at 02:19:38AM -0700, Jason Grout wrote: > > When Mike was experimenting with trac 0.11, he made a plugin or > > something that put a "raw" link next to the attachment link, so an > > attachment would look like: > > > trac_3948_description.patch (raw) Apply on top of previous patches > > > where clicking on trac_... would bring you to the html page, and > > clicking on "raw" would give you the raw attachment. I want this! I need this! +1^(1000!) --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
Robert Miller wrote: > This release is primarily the Python upgrade. The source tarball and > sage.math binary are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.tar.gz > > If you care to try upgrading (do so at your own risk -- upgrading has > been seen to not work, but not seen to work), the bits are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ > Upgrade failed on Fedora 9, 32 bit Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: video for sage days 16
On Thu, Jun 25, 2009 at 9:51 PM, Ondrej Certik wrote: > > Hi, > > On Tue, Jun 23, 2009 at 11:50 PM, William Stein wrote: >> >> Hi, >> >> Video and slides for *all* the talks so far from Sage Days 16 are now >> posted here: >> >> http://wiki.sagemath.org/days16 > > I have embedded the first two videos here: > > http://sage.math.washington.edu/home/ondrej/scratch/sd16/videos.html > > let me know if it works for you in your browser. > > To save bandwidth, I have set the above page *not* to start playing > automatically (neither to start automatically buffer the video), so > you have to click on the video to start playing (and buffering). This > can be trivially changed in the html source code. > > That page also contains a link to the code + info how to embed such videos. > > I am experimenting with that, since youtube only allows ~10 minutes, > vimeo allows more, but restrict to 1 high definition video upload per > week. Here I am hosting the video files on the sage.math server and > that's it, no restrictions. Well, except that I had to convert those > mp4 files to FLV using mencoder (script for doing so is available on > the page above), which might have lost some quality, it was saying > "Skipping frame!" almost all the time on my laptop while converting > the video, so I guess it has some skipped frames, but it looks quite > ok to me. If you figure out how to convert the videos to FLV in some > better way, let me know! That is really amazing!!! William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
fails on sage.math, too On Thu, Jun 25, 2009 at 1:56 PM, Jaap Spies wrote: > > Robert Miller wrote: >> This release is primarily the Python upgrade. The source tarball and >> sage.math binary are here: >> >> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar >> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.tar.gz >> >> If you care to try upgrading (do so at your own risk -- upgrading has >> been seen to not work, but not seen to work), the bits are here: >> >> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ >> > > Upgrade failed on Fedora 9, 32 bit > > Jaap > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
On Thu, Jun 25, 2009 at 11:21 PM, Tom Boothby wrote: > > fails on sage.math, too Just so you know, upgrading from Python 2.5 to Python 2.6 is really hard. At a minimum, doing it right should involve rebuilding *every* Python package in all of Sage. My understanding is that maybe Mike shortcut this by just copying site-packages back over, but I'm worried whether that will work or not (I would be surprised if it did). William > > On Thu, Jun 25, 2009 at 1:56 PM, Jaap Spies wrote: >> >> Robert Miller wrote: >>> This release is primarily the Python upgrade. The source tarball and >>> sage.math binary are here: >>> >>> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar >>> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.tar.gz >>> >>> If you care to try upgrading (do so at your own risk -- upgrading has >>> been seen to not work, but not seen to work), the bits are here: >>> >>> http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ >>> >> >> Upgrade failed on Fedora 9, 32 bit >> >> Jaap >> >> >> > >> > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
These test failures on 32-bit ubuntu (fresh build): .//home/john/sage-4.1.alpha1/devel/sage/doc/common .//home/john/sage-4.1.alpha1/devel/sage/doc/en .//home/john/sage-4.1.alpha1/devel/sage/doc/fr .//home/john/sage-4.1.alpha1/devel/sage/sage after these error messages: ERROR: File .//home/john/sage-4.1.alpha1/devel/sage/doc/common is missing exit code: 1 ERROR: File .//home/john/sage-4.1.alpha1/devel/sage/doc/en is missing exit code: 1 ERROR: File .//home/john/sage-4.1.alpha1/devel/sage/doc/fr is missing exit code: 1 ERROR: File .//home/john/sage-4.1.alpha1/devel/sage/sage is missing exit code: 1 John 2009/6/25 William Stein : > > On Thu, Jun 25, 2009 at 11:21 PM, Tom Boothby wrote: >> >> fails on sage.math, too > > Just so you know, upgrading from Python 2.5 to Python 2.6 is really > hard. At a minimum, doing it right should involve rebuilding *every* > Python package in all of Sage. My understanding is that maybe Mike > shortcut this by just copying site-packages back over, but I'm worried > whether that will work or not (I would be surprised if it did). > > William > >> >> On Thu, Jun 25, 2009 at 1:56 PM, Jaap Spies wrote: >>> >>> Robert Miller wrote: This release is primarily the Python upgrade. The source tarball and sage.math binary are here: http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tar http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-sage.math-only-x86_64-Linux.tar.gz If you care to try upgrading (do so at your own risk -- upgrading has been seen to not work, but not seen to work), the bits are here: http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ >>> >>> Upgrade failed on Fedora 9, 32 bit >>> >>> Jaap >>> >>> >>> > >>> >> >> > >> > > > > -- > William Stein > Associate Professor of Mathematics > University of Washington > http://wstein.org > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
Maybe we should just bump all the version numbers of python packages... I thought this would be a better approach (as did William, who first suggested it), but I wanted to see if upgrading worked with copying site-packages first. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Is MatrixGroup_gap_finite_field and WeylGroup_gens always finite?
Hi,
This weekend I was introducing Sage to a friend. To illustrate Jmol, I
showed him some 3d Cayley graphs of some finite groups :
{{{
sage: S = SymmetricGroup(4)
sage: S.cayley_graph()
Digraph on 24 vertices
}}}
Then, he asked me to show the Cayley graph of some groups he often
works with :
{{{
sage: g = GL(2,GF(3)); g
General Linear Group of degree 2 over Finite Field of size 3
sage: g.order()
48
sage: g.cayley_graph()
Traceback (most recent call last):
...
AttributeError: 'GeneralLinearGroup_finite_field' object has no
attribute 'cayley_graph'
}}}
{{{
sage: G = WeylGroup(['D',4])
sage: G
Weyl Group of type ['D', 4] (as a matrix group acting on the ambient
space)
sage: G.order()
192
sage: G.cayley_graph()
Traceback (most recent call last):
...
AttributeError: 'WeylGroup_gens' object has no attribute
'cayley_graph'
}}}
The reason is that cayley_graph is implemented in the class
sage.groups.group.FiniteGroup but both WeylGroup_gens and
MatrixGroup_gap_finite_field inherits only from
sage.groups.group.Group.
I already begun a patch available in the sage-combinat tree. Mainly,
the changes are :
-class MatrixGroup_gap_finite_field(MatrixGroup_gap):
+class MatrixGroup_gap_finite_field(MatrixGroup_gap, FiniteGroup):
-class WeylGroup_gens(ClearCacheOnPickle, UniqueRepresentation,
MatrixGroup_gens):
+class WeylGroup_gens(ClearCacheOnPickle, UniqueRepresentation,
MatrixGroup_gens, FiniteGroup):
My question is the following : Am I right to assume that both
WeylGroup_gens and MatrixGroup_gap_finite_field are always finite?
Thank you,
Sébastien Labbé
Laboratoire de Combinatoire Informatique Mathématique (LaCIM)
UQAM, Montréal
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: video for sage days 16
Nice video embedding. Btw, it seems the first video is repeated twice (hence the double length). Click to minute 49. Rado On Jun 25, 2:51 pm, Ondrej Certik wrote: > Hi, > > On Tue, Jun 23, 2009 at 11:50 PM, William Stein wrote: > > > Hi, > > > Video and slides for *all* the talks so far from Sage Days 16 are now > > posted here: > > > http://wiki.sagemath.org/days16 > > I have embedded the first two videos here: > > http://sage.math.washington.edu/home/ondrej/scratch/sd16/videos.html > > let me know if it works for you in your browser. > > To save bandwidth, I have set the above page *not* to start playing > automatically (neither to start automatically buffer the video), so > you have to click on the video to start playing (and buffering). This > can be trivially changed in the html source code. > > That page also contains a link to the code + info how to embed such videos. > > I am experimenting with that, since youtube only allows ~10 minutes, > vimeo allows more, but restrict to 1 high definition video upload per > week. Here I am hosting the video files on the sage.math server and > that's it, no restrictions. Well, except that I had to convert those > mp4 files to FLV using mencoder (script for doing so is available on > the page above), which might have lost some quality, it was saying > "Skipping frame!" almost all the time on my laptop while converting > the video, so I guess it has some skipped frames, but it looks quite > ok to me. If you figure out how to convert the videos to FLV in some > better way, let me know! > > Ondrej --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Maxima Errors
Thanks for that explanation, gsw. I feel like I have a better sense of why that happened so often in class! - kcrisman On Jun 25, 4:10 pm, gsw wrote: > Hi, > > I suspect you're just running out of RAM. > Not necessarily physically, but the construction Sage --> expect > interface --> Maxima --> Lisp implementation is a fragile one. If the > Lisp implementation "thinks" it runs out of space, this is not handled > too gracefully by Maxima, and as a consequence the synchronization > between Sage/the expect interface, and Maxima, gets lost more or less > often. > > Three options (none, or all, might help): > - alter your code to do your computations in "smaller pieces" > - move to a "bigger" machine > - use a current Sage version (maybe the clisp ---> ecl switch does > heal your problem, or the pynac switch, or ...) > > Good luck! > > Cheers, > gsw --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
On Jun 25, 11:18 am, Robert Miller wrote: > This release is primarily the Python upgrade. The source tarball and > sage.math binary are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tarhttp://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-s... > > If you care to try upgrading (do so at your own risk -- upgrading has > been seen to not work, but not seen to work), the bits are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ > > I owe much gratitude to Mike Hansen, Martin Albrecht and particularly > William Stein for help with getting the Python upgrade to work. > > These are the known doctest failures: > > sage -t -long devel/sage/sage/modules/ > vector_real_double_dense.pyx # 1 doctests failed > sage -t -long devel/sage/doc/fr/tutorial/programming.rst # 1 > doctests failed > > I haven't looked into these, since I have spent about eleven hours out > of the last thirty on the Python upgrade. > > Tom Boothby will take over for alpha2, and I will merge more spkg's > for alpha3, which will also be rc0. > > Cheers, > > Robert Miller See #6418, which fixes as many of the reference manual warnings for 4.1.alpha1 as I know how to fix. John --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Naming Conventions for Dirac Delta, Heaviside Theta and Unit Step
Hi,
On Tue, Jun 23, 2009 at 6:45 PM, Maurizio wrote:
> Honestly, I don't actually know whether it means that much, but at
> this point I think that it could be useful for us to follow
> Mathematica in defining two different functions: Heaviside which is
> undefined in 0 and that is defined as the function whose derivative is
> the Dirac Delta ( see
> http://functions.wolfram.com/GeneralizedFunctions/HeavisideTheta/02/
> ) and UnitStep, which is the piecewise version of this function, so
> it's numerically defined everywhere. It would be great if one could
> possibly change the desired value in 0.
>
> I think it doesn't hurt now to carry on both, because it shouldn't be
> that difficult to merge them in future if we don't see any usefulness
> in having them separated.
If I gather properly, we are having two different step functions
(at least for now) as
(2) Heaviside:
(a) represented as: "heaviside"
(b) latex name :"H"
(c) heaviside(0): "heaviside(0)"
(3) Unit Step:
(a) represented as: "unit_step"
(b) latex name :"\mathrm{u}"
(c) unit_step(0) = 1
If there are no more suggestions for change, then I will
post a patch adding support for these functions. I have split
up the integration code involving these functions in a
separate file and will post it later.
Cheers,
Golam
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
I got the following on an intel mac, 10.4.11, not sure which are known or unknown issues at this point: The following tests failed: sage -t "devel/sage/doc/fr/tutorial/programming.rst" sage -t "devel/sage/sage/graphs/graph.py" sage -t "devel/sage/sage/misc/darwin_utilities.pyx" sage -t "devel/sage/sage/misc/sagedoc.py" sage -t "devel/sage/sage/parallel/decorate.py" Total time for all tests: 7139.2 seconds -Marshall On Jun 25, 1:18 pm, Robert Miller wrote: > This release is primarily the Python upgrade. The source tarball and > sage.math binary are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tarhttp://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-s... > > If you care to try upgrading (do so at your own risk -- upgrading has > been seen to not work, but not seen to work), the bits are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ > > I owe much gratitude to Mike Hansen, Martin Albrecht and particularly > William Stein for help with getting the Python upgrade to work. > > These are the known doctest failures: > >sage -t -long devel/sage/sage/modules/ > vector_real_double_dense.pyx # 1 doctests failed >sage -t -long devel/sage/doc/fr/tutorial/programming.rst # 1 > doctests failed > > I haven't looked into these, since I have spent about eleven hours out > of the last thirty on the Python upgrade. > > Tom Boothby will take over for alpha2, and I will merge more spkg's > for alpha3, which will also be rc0. > > Cheers, > > Robert Miller --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Naming Conventions for Dirac Delta, Heaviside Theta and Unit Step
On Thu, Jun 25, 2009 at 9:16 PM, Golam Mortuza
Hossain wrote:
>
> Hi,
>
...
>
> If I gather properly, we are having two different step functions
> (at least for now) as
>
> (2) Heaviside:
> (a) represented as: "heaviside"
> (b) latex name :"H"
> (c) heaviside(0): "heaviside(0)"
>
> (3) Unit Step:
> (a) represented as: "unit_step"
> (b) latex name :"\mathrm{u}"
> (c) unit_step(0) = 1
>
> If there are no more suggestions for change, then I will
This looks okay to me.
> post a patch adding support for these functions. I have split
> up the integration code involving these functions in a
> separate file and will post it later.
>
>
> Cheers,
> Golam
>
> >
>
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] problem with complex_plot and real_part
Can someone verify that this is a bug? Any hope a fix? (This is with
sage-4.0.2 on sage.math.)
{{{
sage: complex_plot((x^2 + I).sqrt().real_part(), (-2, 2), (-2, 2))
---
RuntimeError Traceback (most recent call
last)
...
/usr/local/sage/local/lib/python2.5/site-packages/sage/symbolic/
expression.so in sage.symbolic.expression.Expression.operator (sage/
symbolic/expression.cpp:15127)()
RuntimeError: cannot find SFunction in table
}}}
Nick
PS. The following quits with a less than clear error message; it
would be nice if there was some input checking.
{{{
sage: complex_plot((x^2 + I).sqrt(), (-2, 2), (-2, 2)) # I forgot the
real_part
}}}
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage-4.1.alpha1
On 64-bit Fedora 10, I see these doctest failures: sage -t "devel/sage/doc/fr/tutorial/programming.rst" sage -t "devel/sage/sage/misc/darwin_utilities.pyx" Kiran On Jun 25, 2:18 pm, Robert Miller wrote: > This release is primarily the Python upgrade. The source tarball and > sage.math binary are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1.tarhttp://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1-s... > > If you care to try upgrading (do so at your own risk -- upgrading has > been seen to not work, but not seen to work), the bits are here: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha1/ > > I owe much gratitude to Mike Hansen, Martin Albrecht and particularly > William Stein for help with getting the Python upgrade to work. > > These are the known doctest failures: > >sage -t -long devel/sage/sage/modules/ > vector_real_double_dense.pyx # 1 doctests failed >sage -t -long devel/sage/doc/fr/tutorial/programming.rst # 1 > doctests failed > > I haven't looked into these, since I have spent about eleven hours out > of the last thirty on the Python upgrade. > > Tom Boothby will take over for alpha2, and I will merge more spkg's > for alpha3, which will also be rc0. > > Cheers, > > Robert Miller --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Is MatrixGroup_gap_finite_field and WeylGroup_gens always finite?
Hi Sébastien!
On Thu, Jun 25, 2009 at 03:06:15PM -0700, slabbe wrote:
> This weekend I was introducing Sage to a friend. To illustrate Jmol, I
> showed him some 3d Cayley graphs of some finite groups :
>
> {{{
> sage: S = SymmetricGroup(4)
> sage: S.cayley_graph()
> Digraph on 24 vertices
> }}}
>
> Then, he asked me to show the Cayley graph of some groups he often
> works with :
>
> {{{
> sage: g = GL(2,GF(3)); g
> General Linear Group of degree 2 over Finite Field of size 3
> sage: g.order()
> 48
> sage: g.cayley_graph()
> Traceback (most recent call last):
> ...
> AttributeError: 'GeneralLinearGroup_finite_field' object has no
> attribute 'cayley_graph'
> }}}
>
>
> {{{
> sage: G = WeylGroup(['D',4])
> sage: G
> Weyl Group of type ['D', 4] (as a matrix group acting on the ambient
> space)
> sage: G.order()
> 192
> sage: G.cayley_graph()
> Traceback (most recent call last):
> ...
> AttributeError: 'WeylGroup_gens' object has no attribute
> 'cayley_graph'
> }}}
>
> The reason is that cayley_graph is implemented in the class
> sage.groups.group.FiniteGroup but both WeylGroup_gens and
> MatrixGroup_gap_finite_field inherits only from
> sage.groups.group.Group.
>
> I already begun a patch available in the sage-combinat tree. Mainly,
> the changes are :
>
> -class MatrixGroup_gap_finite_field(MatrixGroup_gap):
> +class MatrixGroup_gap_finite_field(MatrixGroup_gap, FiniteGroup):
>
> -class WeylGroup_gens(ClearCacheOnPickle, UniqueRepresentation,
> MatrixGroup_gens):
> +class WeylGroup_gens(ClearCacheOnPickle, UniqueRepresentation,
> MatrixGroup_gens, FiniteGroup):
>
> My question is the following : Am I right to assume that both
> WeylGroup_gens and MatrixGroup_gap_finite_field are always finite?
MatrixGroup_gap_finite_field, yes, I think so.
But for WeylGroup not necessarily: this also is used to build affine
Weyl groups which are infinite. On the other hand the upcoming root
system patch puts Weyl groups in the appropriate category:
FiniteWeylGroups() or AffineWeylGroups() or ... That's one of the
point of the category stuff: to be able to customize the inheritance
at run time depending on the properties of the parent one is
constructing.
That's not the complete end of the story though, since Cayley graphs
are currently implemented at two spots:
- Once in the abstract class FiniteGroup
- Once in the category FiniteSemigroups
This remains to be cleaned up, by merging the two implementations into
the FiniteSemigroups category. If I recall correctly, there are couple
things one wants to do differently for finite groups, so probably the
(yet to be created) category FiniteGroups will need to further
override/customize the Cayley graph method.
Do you feel like doing it? That would be great!
Cheers, Nicolas
--
Nicolas M. Thiéry "Isil"
http://Nicolas.Thiery.name/
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: patch naming scheme on trac
On Wed, Jun 24, 2009 at 01:46:29PM -0700, Robert Miller wrote: > > On Jun 24, 10:34 pm, Robert Miller wrote: > > > I really like having the ticket number first, it makes it easy to see > > > (given an ordered list of patches) what patches belong as part of a > > > single ticket. E.g. > > > > > 6201-heegner.patch > > > 6201-referee-fixes.patch > > > ... > > > > +1 If just one could tolerate also a description field before the number, imposing it to be identical for all patches in the ticket, that would do as well. Oh, and if you really want a prefix, sage_... would be more specific than trac_ (many projects use trac) > Something occurs to me, which is that the sage-combinat group spends a > lot of time working on patches outside of trac. This is probably why > Nicolas prefers to have them organized by concept. But for me, I'm > always on trac-- everything I work on, even experimental, has a trac > ticket. I generally tend to have several tickets open in Firefox so I > know which issues I'm tracking. Then I just tab over to the relevant > ticket, and that's why trac_### is so useful. Since we are discussing > naming conventions for patches which are on trac, maybe we should keep > that in mind. > > Maybe the combinat group can discuss a related scheme, and have > conversion tools which make it effortless to swap between the two > schemes (I'm not volunteering here, just so nobody gives the usual > response :-) ). Oh well, I guess I'll just end up doing this. Btw: would it be easy to extract from the current automated release tools a python function that given a ticket number would return the url's of the corresponding patches on trac? > I'd also like to point out that one of the biggest reasons projects > fail is due to trying to change their tools midstream, which is one > argument for keeping the convention the way it is. However, that is > precisely what the combinat group would have to do to adapt to this > scheme. This is why I recommend automated conversion tools. > Another point to make is a video I saw recently by the SVN guys, who > claimed that the amount of discussion which centers around a decision > is inversely proportional to how important it is. They related a story > where the project nearly forked and many feelings were hurt over > something ten times more trivial than this topic. Just for perspective. Definitely. Speak of pickling for the category stuff ... But yeah I am being grumpy, and mainly needed to express my disagreement a last time, in preparation for the future complaints of our developers about the yet another little grain of complexity of having different patch names on trac and on sage-combinat server. Best, Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
