[sage-devel] Most 3.4.1 binaries are available in http://www.sagemath.org/bin/
Hello folks, nearly all binaries for 3.4.1 are available in http://www.sagemath.org/bin/ (as the title says). All x86 and x86-64 Linux binary as well as the VMWare image are now SSE2 only, i.e. there are some performance regressions as mentioned yesterday in a thread here, for example RDF matrix matrix multiply. The binaries are currently mirroring out, so you might want to check your local mirror first (even thought right now only the two Seattle sites have complete sets of binaries) while the Boston mirror is catching up right now. Anyway, take them for a spin if you have waited for binaries and let us know if they work. The official announcement for 3.4.1 should go out tomorrow. Cheers, Michael --~--~-~--~~~---~--~~ 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.0 release plan ; categories
On Wed, Apr 22, 2009 at 06:24:38PM -0700, mabshoff wrote: > while there should be a quick 3.4.2 to mop up patches from trac before > the big 4.0 jump today we had a planning session during the UW status > meeting about the goals for Sage 4.0. The result is at > >http://wiki.sagemath.org/plan/sage-4.0 > > It still needs a little polish, i.e. the issues for Solaris as well as > 64 bit OSX support need to be fleshed out, but the 75% coverage target > has a lot of concrete projects and/or suggestions on what to attack. > If anyone has some other suggestions for large projects that are > doable in the next 3 weeks please let us know. I really would want to get the category code in Sage soon (4.0???): - Rebasing the patch after each Sage release is a real pain in the neck - The time frame where I can focus on working on this patch is closing (essentially it has to be done before June) - FPSAC is approaching - My coming to Seattle in a couple weeks is a perfect time to put some hard work on it - I am myself convinced that the patch is mature, and the remaining technical issues can be solved within a reasonable time frame (e.g. up to backward compatibility that just needs to be taken care of, pickling works). Now I need to convince you guys :-) To this end, I created http://sagetrac.org/sage_trac/ticket/5891, which includes a status report. This report also appears in the description header of the patch on the sage-combinat patch server, which I'll try to update on a regular basis. I also started to write a elements/parents/category primer, which I beta tested on the Sage developers in Davis. I will need your help! And to start with a review on #5120 :-) Also, if you really need to modify any of file listed below, please double check the patch and synchronize with me (most of the changes are trivial import updates). Michael: if you spot a patch doing so, please ping me. Cheers, Nicolas M sage/algebras/group_algebra.py M sage/algebras/steenrod_algebra.py M sage/categories/__init__.py M sage/categories/action.pyx M sage/categories/all.py M sage/categories/category.py M sage/categories/category_types.py M sage/categories/functor.pyx M sage/categories/homset.py M sage/categories/map.pyx M sage/categories/morphism.pyx M sage/categories/pushout.py M sage/combinat/combinatorial_algebra.py M sage/combinat/free_module.py M sage/combinat/permutation.py M sage/combinat/schubert_polynomial.py M sage/combinat/species/series.py M sage/combinat/symmetric_group_algebra.py M sage/groups/group.pyx M sage/groups/matrix_gps/homset.py M sage/groups/perm_gps/permgroup.py M sage/groups/perm_gps/permgroup_named.py M sage/matrix/matrix_space.py M sage/misc/misc.py M sage/modular/abvar/homspace.py M sage/modular/hecke/degenmap.py M sage/modular/hecke/hecke_operator.py M sage/modular/hecke/homspace.py M sage/modular/hecke/module.py M sage/modular/hecke/morphism.py M sage/modular/modsym/ambient.py M sage/modules/free_module.py M sage/modules/matrix_morphism.py M sage/modules/module.pyx M sage/probability/random_variable.py M sage/rings/homset.py M sage/rings/integer.pyx M sage/rings/morphism.pyx M sage/rings/residue_field.pyx M sage/rings/ring.pyx M sage/schemes/generic/homset.py M sage/schemes/generic/scheme.py M sage/schemes/generic/spec.py M sage/schemes/hyperelliptic_curves/kummer_surface.py M sage/sets/all.py M sage/sets/set.py M sage/structure/category_object.pyx M sage/structure/element.pyx M sage/structure/parent.pyx M sage/structure/parent_base.pyx M sage/structure/parent_gens.pyx M sage/structure/parent_old.pyx M sage/structure/wrapper_parent.pyx -- 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: more trouble with comparisons
>
> Translation, if it's not clear. It got a coercion map f, tried to
> call f(x), and f(x) returned None which is clearly a bug for whoever
> implemented the morphism in question.
>
That helped me track it down to
{{{
sage: X = Spec(ZZ)
sage: H = Homset(X, X)
sage: H(X.identity_morphism())
}}}
Note the absence of output from the last command -- that's the None
that's creating all the trouble. OK, I think I can fix this now.
Robert and William, thanks for the help!
Alex
--
Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne
-- Australia -- http://www.ms.unimelb.edu.au/~aghitza/
--~--~-~--~~~---~--~~
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: more trouble with comparisons
On Apr 25, 2009, at 12:40 AM, Alex Ghitza wrote:
>
>>
>> Translation, if it's not clear. It got a coercion map f, tried to
>> call f(x), and f(x) returned None which is clearly a bug for whoever
>> implemented the morphism in question.
>>
>
> That helped me track it down to
>
> {{{
> sage: X = Spec(ZZ)
> sage: H = Homset(X, X)
> sage: H(X.identity_morphism())
> }}}
>
> Note the absence of output from the last command -- that's the None
> that's creating all the trouble. OK, I think I can fix this now.
Good.
BTW, there's a ticket up to make this kind of stuff easier to debug:
http://sagetrac.org/sage_trac/ticket/5596
- 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] Gpu Computing...
Hi All, Is there anyone who has knowledge about it and its possible future benefits to scientific computing (especially for sage + maxima etc.) of the GPU computing with the new Nvidia Tesla platform? http://www.nvidia.com/object/tesla_computing_solutions.html Quote: "Powered by the Tesla C1060 Computing Processor, the NVIDIA Tesla Personal Supercomputer delivers cluster level computing performance on your desk—250 times faster than standard PCs and workstations." Regards AAP --~--~-~--~~~---~--~~ 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: Gpu Computing...
On Apr 25, 2:15 am, ahmet alper parker wrote: > Hi All, > > Is there anyone who has knowledge about it and its possible future > benefits to scientific computing (especially for sage + maxima etc.) > of the GPU computing with the new Nvidia Tesla platform? > > http://www.nvidia.com/object/tesla_computing_solutions.html > > Quote: > "Powered by the Tesla C1060 Computing Processor, the NVIDIA Tesla > Personal Supercomputer delivers cluster level computing performance on > your desk—250 times faster than standard PCs and workstations."> We have played around with GPUs to do exact and numerical linear algebra in Sage and unfortunately have not merged any of that code yet. The factor 250 speedup is plain bullshit marketing numbers and only doable in a very, very few special cases (well, and some of the quad CPU card systems Nvidia sells retail for more than $10k, so not exactly comparing apples and apples here). Something more realistic is maybe a factor 2 to 10 for some operations - not too shabby, but given the cost and the technical requirements anything but trivial to do. > Regards > > AAP Cheers, Michael --~--~-~--~~~---~--~~ 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.0 release plan ; categories
On Apr 25, 12:13 am, "Nicolas M. Thiery" wrote: > On Wed, Apr 22, 2009 at 06:24:38PM -0700, mabshoff wrote: Hi Nicolas, > I really would want to get the category code in Sage soon (4.0???): At this stage I do believe you might have a hard time getting this into 4.0 given the time frame and the ToDo list, but we will see what happens :) > - Rebasing the patch after each Sage release is a real pain in the neck Yeah, I can imagine. Is this patch splittable in any sane set of patches, i.e. for coercion the big patch bomb did not go in at once, but only the initial infrastructure, then later one by one classes were converted? If this is possible with this patch or is it "all or nothing" > - The time frame where I can focus on working on this patch is closing > (essentially it has to be done before June) > > - FPSAC is approaching > > - My coming to Seattle in a couple weeks is a perfect time to put > some hard work on it > > - I am myself convinced that the patch is mature, and the remaining > technical issues can be solved within a reasonable time frame > (e.g. up to backward compatibility that just needs to be taken care > of, pickling works). Now I need to convince you guys :-) > > To this end, I createdhttp://sagetrac.org/sage_trac/ticket/5891, > which includes a status report. This report also appears in the > description header of the patch on the sage-combinat patch server, > which I'll try to update on a regular basis. I also started to write a > elements/parents/category primer, which I beta tested on the Sage > developers in Davis. > > I will need your help! And to start with a review on #5120 :-) Aren't there major design issues like dynamic classes to be discussed first? You mentioned a design document you were writing with Florent - is that around yet? The ToDo list also mentions that you are still working on having this work with Cython classes. Can you elaborate on that a little? > Also, if you really need to modify any of file listed below, please > double check the patch and synchronize with me (most of the changes > are trivial import updates). Michael: if you spot a patch doing so, > please ping me. Ok, but I am pretty sure due to many doctesting patches as well as work on ReSTifying documentation many patches will be touched. > Cheers, > Nicolas Cheers, Michael --~--~-~--~~~---~--~~ 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: comparison of morphisms
3. as I mentioned, I looked in rings/morphism.pyx for inspiration; this helped, but not enough so I tried sage: f = ZZ.hom(QQ) sage: g = loads(dumps(f)) sage: f == g False Shouldn't this return True? >> >> Yes >> Shouldn't a test like this be somewhere in rings/morphism.pyx? >> >> Yes. >> > > This is now http://trac.sagemath.org/sage_trac/ticket/5820 > And there is now a fairly trivial patch solving this at http://trac.sagemath.org/sage_trac/ticket/5820 -- Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne -- Australia -- http://www.ms.unimelb.edu.au/~aghitza/ --~--~-~--~~~---~--~~ 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 3.4.2.alpha0 released!
Wow! I have stunning news (for me anyway): This compiles perfectly *and passes all tests* on ubuntu 64bit 8.10 with a phenom chip. This is the first time that has happened in more releases than I can remember! Great job to everyone involed, which definitely includes Michael Abshoff. On Fri, Apr 24, 2009 at 6:07 AM, mabshoff wrote: > > Hello folks, > > here goes 3.4.2.alpha0. It does not contain all the fixes I wanted, > but I merged two large (200kb+) patches (#5610 and #5848) that touched > a lot of files and that were in danger of bitrotting. Since I > considered it pointless to force people to rebase potentially twice I > pulled them both into alpha0. > > The source, upgrade bits and a sage.math-only binary should be > available in > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.2/ > > From here on the plan is to merge other reviewed patches (in case you > are bored, there are about 80 patches to review in trac), fix some > more issues and then get out rc0 on Sunday to have 3.4.2.final very > early next week. Coverage right now is at 69% and there is a doctest > patch for padics that brings that directory to 100% and gives us 2.1% > globally, so I definitely want that one merged. Another thing to > review and push hard are the pynac tickets and the not yet in trac > patch for the symbolics switch. Mike Hansen mentioned he could post > something today, so hopefully it will get reviewed until Sunday and > merged to give the code a good beating during 3.4.2. > > If you have any patches in trac please make sure to check if they > apply to alpha0 since they will get bounced back if they fail to > merge. > > Cheers, > > Michael > > Merged in Sage 3.4.2.alpha0: > > #4809: Dan Drake, John Palmieri: the installation guide and > constructions guide should be CC licensed [Reviewed by John Palmieri, > Dan Drake] > #5111: Mike Hansen, Bill Page: axiom --> fricas [Reviewed by Carl > Witty] > #5130: R. Andrew Ohana: create a prime_pi function that doesn't just > compute len(prime_range(n) [Reviewed by Carl Witty, William Stein, > Michael Abshoff] > #5346: John Cremona: Some doctests in schemes/elliptic_curves/ > ell_rational_field.py fail with optional database installed [Reviewed > by Michael Abshoff] > #5567: Wilfried Huss: bug in region_plot [Reviewed by Bill Cauchois] > #5595: Robert Bradshaw: minor dependancy checking glitch [Reviewed by > Carl Witty] > #5610: John Palmieri: LaTeX customization [Reviewed by Robert > Bradshaw, Rob Beezer] > #5627: Karl-Dieter Crisman: Trivial typo in quadratic_nonresidue > [Reviewed by Minh Van Nguyen] > #5704: John Cremona: Implementation of finding elliptic curves with > prescribed reduction over QQ [Reviewed by Robert Miller] > #5751: Dan Bump: cartan_type now a method rather than attribute in > weyl_characters.py [Reviewed by Anne Schilling] > #5795: Simon King: Improved performance of > MPolynomialRing_libsingular.__call__() [Reviewed by Martin Albrecht] > #5803: Robert Bradshaw: Upgrade Cython to 0.11.1 [Reviewed by William > Stein] > #5809: Alex Ghitza: schemes/generic/hypersurface.py is completely > broken [Reviewed by John Cremona] > #5815: Mitesh Patel, Jason Grout: Disable TinyMCE in the live > documentation [Reviewed by Jason Grout, Mitesh Patel] > #5821: Robert Bradshaw: preparser incorrectly handles backslash > operator inside strings (sometimes) [Reviewed by Carl Witty] > #5822: William Stein: cusps -- implement action of the Galois group on > cusps for congruence subgroups as on page 12 of Steven's "Arithmetic > on Modular Curves" [Reviewed by John Cremona] > #5836: Jason Grout: Make show() immediately show an image in the > notebook [Reviewed by William Stein] > #5848: John Palmieri: untabify Sage [Reviewed by Rob Beezer, Michael > Abshoff] > #5851: Chris Wuthrich: Convert 3 more elliptic curves files to ReST > and add to reference manual [Reviewed by John Cremona] > #5861: Michael Abshoff: Remove cocoa, four_ti_2, reduce and template > interfaces since they do not work/are broken [Reviewed by Michael > Abshoff] > #5863: John Palmieri: remove some files from sage/algebras [Reviewed > by William Stein] > #5871: William Stein: solaris x86 3.4.1 -- code_bounds.py fails some > plot doctests [Reviewed by Michael Abshoff] > #5876: John Cremona: Vast speedup in P1List construction [Reviewed by > William Stein, Robert Bradshaw] > #5886: William Stein: Bug in free module homomorphism creation > [Reviewed by Robert Bradshaw] > > > > > --~--~-~--~~~---~--~~ 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_Integer() function semantics
> How could you not notice? If I do is_Integer I get a big DeprecationWarning: > Does your Sage not do that? The reason I did not notice it is that is_Integer() was in the body of a main loop and no warnings were printed. For example, [n for n in range(0,10) if is_Integer(n+1)] returns [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] However [n for n in range(0,10) if is_Integer(n)] returns null list [ ] In the first case the answer was correct and in the second case the answer was wrong. In both cases, please note no warning was printed. My sage version is 3.4 and using it on Mac OS X. I am using Robert's solution. It seems to work well. Thanks, Nirmal --~--~-~--~~~---~--~~ 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_Integer() function semantics
> How could you not notice? If I do is_Integer I get a big DeprecationWarning: > Does your Sage not do that? The reason I did not notice it is that is_Integer() was in the body of a main loop and no warnings were printed. For example, [n for n in range(0,10) if is_Integer(n+1)] returns [0, 1, 2, 3, 4, 5, 6, 7, 8, 9] However [n for n in range(0,10) if is_Integer(n)] returns null list [ ] In the first case the answer was correct and in the second case the answer was wrong. In both cases, please note no warning was printed. My sage version is 3.4 and using it on Mac OS X. I am using Robert's solution. It seems to work well. Thanks, Nirmal --~--~-~--~~~---~--~~ 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.0 release plan ; categories
> At this stage I do believe you might have a hard time getting this > into 4.0 given the time frame and the ToDo list, but we will see what > happens :) I let you pickup the best option. > Aren't there major design issues like dynamic classes to be > discussed first? You mentioned a design document you were writing > with Florent - is that around yet? The discussions at MSRI were pretty useful, so from my point of view there just remains a couple minor design decisions. Of course, I definitely still need to make my point for the decision I have taken :-) This is the current main purpose of the primer (still a draft though). > The ToDo list also mentions that you are still working on having > this work with Cython classes. Can you elaborate on that a little? I guess 10 lines of code will be worth 10 pages of discussion. I'll try to write a proof of concept next week. > > Also, if you really need to modify any of file listed below, please > > double check the patch and synchronize with me (most of the changes > > are trivial import updates). Michael: if you spot a patch doing so, > > please ping me. > > Ok, but I am pretty sure due to many doctesting patches as well as > work on ReSTifying documentation many patches will be touched. Precisely: do we really need to doctest right now things that are about to change soon? For example, the recent doctesting of sage/categories/morphisms.py made me loose quite some time. > splitting of the patch bomb: Before posting the patch to trac, I'll split it up into: - patch with all trivial import updates (the most invasive one) - main patch with the category framework (with updates to parents/morphism/...) and the categories themselves this one is hard to split further - patch updating about 10 existing sage classes with too many interdependencies to be updated later on (morphisms) - patches with applications (combinatorial free modules, sf, ...) But this is really to split the reviewing process by area of expertise. There are a lot of interdependencies, so I don't think we can apply only a subset and still maintain 100% positive tests. Sage probably won't even run without applying all three first patches. 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: Sage 4.0 release plan ; categories
On Sat, Apr 25, 2009 at 8:39 AM, Nicolas M. Thiery wrote: > >> At this stage I do believe you might have a hard time getting this >> into 4.0 given the time frame and the ToDo list, but we will see what >> happens :) > > I let you pickup the best option. > >> Aren't there major design issues like dynamic classes to be >> discussed first? You mentioned a design document you were writing >> with Florent - is that around yet? > > The discussions at MSRI were pretty useful, so from my point of view > there just remains a couple minor design decisions. Of course, I > definitely still need to make my point for the decision I have taken :-) > This is the current main purpose of the primer (still a draft though). > >> The ToDo list also mentions that you are still working on having >> this work with Cython classes. Can you elaborate on that a little? > > I guess 10 lines of code will be worth 10 pages of discussion. I'll > try to write a proof of concept next week. > >> > Also, if you really need to modify any of file listed below, please >> > double check the patch and synchronize with me (most of the changes >> > are trivial import updates). Michael: if you spot a patch doing so, >> > please ping me. >> >> Ok, but I am pretty sure due to many doctesting patches as well as >> work on ReSTifying documentation many patches will be touched. > > Precisely: do we really need to doctest right now things that are > about to change soon? For example, the recent doctesting of > sage/categories/morphisms.py made me loose quite some time. Just for the record, I hate when there is a looming patch over months of time whose main impact on Sage is to keep the rest of Sage from improving in quality. For example, with Bill Furnish working on symoblic for months, the main longterm impact on Sage was that nobody improved any of the calculus doctests. Two days ago I sat down to do some work on implementing general modules over a PID and decided to add some doctests to modules/*. I quickly found a *major* bug in categories/morphisms.py, and you better believe I fixed it and kept adding doctests. So I'm against people not fixing and improving code, just because it is in your list. >> splitting of the patch bomb: > > Before posting the patch to trac, I'll split it up into: > > - patch with all trivial import updates (the most invasive one) > - main patch with the category framework (with updates to > parents/morphism/...) > and the categories themselves > this one is hard to split further > - patch updating about 10 existing sage classes with too many > interdependencies to be updated later on (morphisms) > - patches with applications (combinatorial free modules, sf, ...) > > But this is really to split the reviewing process by area of > expertise. There are a lot of interdependencies, so I don't think we > can apply only a subset and still maintain 100% positive tests. Sage > probably won't even run without applying all three first patches. > > Cheers, > Nicolas > -- > Nicolas M. Thiéry "Isil" > http://Nicolas.Thiery.name/ > > > > -- 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: is_Integer() function semantics
> [n for n in range(0,10) if is_Integer(n+1)]
snip
> [n for n in range(0,10) if is_Integer(n)]
You are doing this from the command line, yes? The first is getting
preparsed, so that 1 is not a python int, it is a sage Integer:
sage: preparse('[n for n in range(0,10) if is_Integer(n+1)]')
'[n for n in range(Integer(0),Integer(10)) if is_Integer(n+Integer(1))]'
sage: preparse('[n for n in range(0,10) if is_Integer(n)]')
'[n for n in range(Integer(0),Integer(10)) if is_Integer(n)]'
As for the warnings not being printed, in the loop you are maybe not
considered to be in Python global scope? I cannot say.
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] Trouble building 3.4.1 on Mac Pro
Hi, I'm having trouble with building gmp-mpir in sage 3.4.1 on my Mac Pro. I have previously successfully built 3.1.2 without any difficulty. Any comments are appreciated. Thanks, -Jon =) --- The Hardware overview is Model Name:Mac Pro Model Identifier:MacPro3,1 Processor Name:Quad-Core Intel Xeon Processor Speed:2.8 GHz Number Of Processors:2 Total Number Of Cores:8 L2 Cache (per processor):12 MB Memory:16 GB Bus Speed:1.6 GHz Boot ROM Version:MP31.006C.B05 SMC Version:1.25f4 and the end of the logfile looks like ... gmp-mpir-1.1/src/dumbmp.c gmp-mpir-1.1/src/assert.c gmp-mpir-1.1/src/cpuid.c gmp-mpir-1.1/src/AUTHORS Finished extraction Host system uname -a: Darwin d447-614121.math.uga.edu 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 i386 GCC Version gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /var/tmp/gcc/gcc-5465~16/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include -dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin9 --with-arch=apple --with-tune=generic --host=i686-apple-darwin9 --target=i686-apple-darwin9 Thread model: posix gcc version 4.0.1 (Apple Inc. build 5465) Deleting assembly files which depend on PIC assembly working or 32 bit OSX on Intel hardware checking build system type... Invalid configuration `penryn-apple-darwin9.6.0': machine `penryn-apple' not recognized configure: error: /bin/sh ./config.sub penryn-apple-darwin9.6.0 failed Failed to configure. real0m0.637s user0m0.226s sys 0m0.445s sage: An error occurred while installing gmp-mpir-1.1 --~--~-~--~~~---~--~~ 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_Integer() function semantics
> snip > > > [n for n in range(0,10) if is_Integer(n)] > > You are doing this from the command line, yes? I am doing this in the notebook() -Nirmal --~--~-~--~~~---~--~~ 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 and symbolic software design
Hi: I just started preparing for a talk next Friday in an NSF workshop on "Future Directions of Computaton Research" in the "Symbolic Software Design" section. Therefore, I think I should say something about the work on pynac and how it will be replacing maxima. I tried the wiki to see what was there on this but the wiki seems to be down. Any suggestions on other references or ideas on how to present this? I really want to present Sage in as positive light as possible, which being accurate and succinct. I was plannning on getting ideas from the long version of the "White paper" William and I wrote http://sage.math.washington.edu/home/wdj/research/oscas-nsf-white-paper12.pdf but am more than happy to listen to other suggestions. - David --~--~-~--~~~---~--~~ 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: Trouble building 3.4.1 on Mac Pro
On Apr 25, 10:04 am, Jonathan Hanke wrote: > Hi, > > I'm having trouble with building gmp-mpir in sage 3.4.1 on my Mac Pro. I > have previously successfully built 3.1.2 without any difficulty. Any > comments are appreciated. Thanks, > > -Jon > =) Hi Jon, The issue is known and has been fixed in usptream MPIR. There should be an updated MPIR.spkg available at #5849 shortly. Cheers, Michael --~--~-~--~~~---~--~~ 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] C++ and Cython
This summer Danilo Freitas got accepted to work on better C++ support for Cython as a GSoC project. This is a great opportunity to make it easier to wrap and use C++ code from Python. We are still in the planning stages, and I want to get input from those who've used both: what do you want to see by the end of the summer? Taken to the limit, this could be much longer than a summer project, so we're looking for direction from the community to focus our energy and direction. The two questions I'm most interested in are 1) Do you have any priorities for features you'd like to see sooner rather than later? 2) What would be *your* preferred syntax for declaring a templated, operator-overloading class in C++? A wiki page has been started at http://wiki.cython.org/enhancements/ cpp , currently it's mostly a dumping ground for random ideas that have yet to be fleshed out. - 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] boehm_gc in Sage
Hello, I was wondering why boehm_gc is a standard Sage package. It seems that it isn't actually a dependency of anything in spkg/standard/deps; is that because it is only used by the sage library and a there's a missing dependency, or is something else going on? -Tim Abbott --~--~-~--~~~---~--~~ 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 3.4.2.alpha0 released!
On Apr 24, 2009, at 03:07 , mabshoff wrote: > here goes 3.4.2.alpha0. It does not contain all the fixes I wanted, > but I merged two large (200kb+) patches (#5610 and #5848) that touched > a lot of files and that were in danger of bitrotting. Since I > considered it pointless to force people to rebase potentially twice I > pulled them both into alpha0. > > The source, upgrade bits and a sage.math-only binary should be > available in > >http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.2/ Built as an upgrade (starting with 3.4.1.rc1 -> rc2 -> rc4) on Mac OS X, 10.5.6, Dual Quad Xeon/Mac Pro2,1. No problems in the build. All tests passed! Justin -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds --- My wife 'n kids 'n dogs are gone, I can't get Jesus on the phone, But Ol' Milwaukee's Best is my best friend. --- --~--~-~--~~~---~--~~ 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: load/attach bugs
Sweet, I will give it a shot. One last thing I noticed is that attached_files() is not exposed to the user. Again not sure if this is how its supposed to work or an actual bug. But if one can attach without refering to a library it would make sense to see what is currently attached again without extra work. Or at least the doc should be clearer on this. Here is what I mean: in command line: sage:attach test.py sage:attached_files() < fail, NameError: name 'attach_files' is not defined sage:sage.misc.interpreter.attached_files()On Fri, Apr 24, 2009 at 9:07 PM, Rado wrote: > > > Alright I got how to make ``load "test space.py"`` work for the > > notebook too. The problem is in: > > > /home/rado/sage-3.4/devel/sage/sage/server/notebook/worksheet.py > > > line 3558: for filename in L.split(): > > > the python split function splits "test space.py" to '"test' and > > 'space.py"'. I googled for a bit and found here > >http://stackoverflow.com/questions/79968/split-a-string-by-spaces-pre... > > that there is part of the python standard library for splitting > > shell. > > > The fix is simple, just use > > > import shlex > > for filename in shlex.split(L): > > > I tried it at it works. > > > I am completely new to software development, so don't know how to > > submit a patch (if this is patch-worthy). But at least now it is on > > the forum so stubborn people with spaces in their folder names can > > google this fix:) > > > Rado > > I think it would be awesome if you would fix this, and submit a patch! > Then you'll get official credit, and have really fully contributed to > Sage. > > You can read the Sage Developer Guide: > http://sagemath.org/doc/developer/ > > The short answer about how to make a patch is: > > (1) change devel/sage/sage/stuff > (2) sage: hg_sage.ci() > (3) sage: hg_sage.export('tip') > (4) copy the resulting numbered_file.patch somewhere. > > -- 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: boehm_gc in Sage
On Apr 25, 2:44 pm, Tim Abbott wrote: > Hello, Hi Tim, > I was wondering why boehm_gc is a standard Sage package. It seems that it > isn't actually a dependency of anything in spkg/standard/deps; is that > because it is only used by the sage library and a there's a missing > dependency, or is something else going on? boehm_gc is required by ecl - at least the way we will build ecl since the default tarball of ecl ships with outdated copies of gmp and boehm_gc. The switch from clisp to ecl has been long delayed, but it ought to be in 4.0 since clisp 2.47 still does not build on Solaris or the current Mandriva release without using an ancient compiler, i.e. on Solaris/Sparc you need gcc 3.2.3 to get a somewhat working clisp. > -Tim Abbott Cheers, Michael --~--~-~--~~~---~--~~ 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: boehm_gc in Sage
On Sat, 25 Apr 2009, mabshoff wrote: > boehm_gc is required by ecl - at least the way we will build ecl since > the default tarball of ecl ships with outdated copies of gmp and > boehm_gc. The switch from clisp to ecl has been long delayed, but it > ought to be in 4.0 since clisp 2.47 still does not build on Solaris or > the current Mandriva release without using an ancient compiler, i.e. > on Solaris/Sparc you need gcc 3.2.3 to get a somewhat working clisp. Okay, so it is indeed currently unused but that is expected to change soon. Good to know. Thanks, -Tim Abbott --~--~-~--~~~---~--~~ 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 3.4.2.alpha0 released!
On Apr 25, 5:53 am, David Joyner wrote: Hi David, > Wow! I have stunning news (for me anyway): > > This compiles perfectly *and passes all tests* on ubuntu 64bit 8.10 > with a phenom chip. Well, give the trouble you have seen in the past with your specific setup this clearly indicates clisp since that is the only real change that made a difference. On some systems clisp 2.47 now completely blows up when building, i.e. both current 32 and 64 bit Madriva releases, where 2.46 did build, so I am glad we will be getting rid of it. I am truly hoping ecl will act more stable, but our dependency on Maxima will decrease with the switch to pynac anyways. > This is the first time that has happened in more releases than I can remember! > > Great job to everyone involed, which definitely includes Michael > Abshoff. :) Cheers, Michael --~--~-~--~~~---~--~~ 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: load/attach bugs
On Sat, Apr 25, 2009 at 4:30 PM, Rado wrote: > > Sweet, I will give it a shot. > > One last thing I noticed is that attached_files() is not exposed to > the user. Again not sure if this is how its supposed to work or an > actual bug. But if one can attach without refering to a library it > would make sense to see what is currently attached again without extra > work. Or at least the doc should be clearer on this. Here is what I > mean: > > in command line: > sage:attach test.py > sage:attached_files() < fail, NameError: name 'attach_files' is > not defined > sage:sage.misc.interpreter.attached_files()> in notebook: > sage:attach test.py > sage:attached_files() < fail, AttributeError: 'module' object has > no attribute 'attached_files' > sage:w.attached_files() <--- this should work theoretically, once I > figure out how to get a hold of the current worksheet and assign it to > w. Any ideas? > attached_files *used* to be available on the command line. Somebody must have removed it. Just add importing it back in misc/all_cmdline.py.For the notebook, the function sage.misc.interpreter.attached_files() actually does *not* give the attached files, so don't add it to all_notebook.py, unless it is fixed to give the attached files. 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] showcase your new features in Sage 3.4.1
Hi folks, The release tour for Sage 3.4.1 is pretty much done now. You can find it at http://wiki.sagemath.org/sage-3.4.1 Just in case I've forgotten to showcase new features you've introduced in Sage 3.4.1, this is a friendly reminder for you to alert me to them or for you to do it yourself. The release tour will be announced in the next few days for the whole world to know about the cool new features you've introduced into 3.4.1. -- 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: showcase your new features in Sage 3.4.1
Just wanted to thank you for the awesome job you've done on the release tour. It's really impressive work. I personally find it very useful. Bill. On 26 Apr, 02:48, Minh Nguyen wrote: > Hi folks, > > The release tour for Sage 3.4.1 is pretty much done now. You can find it at > > http://wiki.sagemath.org/sage-3.4.1 > > Just in case I've forgotten to showcase new features you've introduced > in Sage 3.4.1, this is a friendly reminder for you to alert me to them > or for you to do it yourself. The release tour will be announced in > the next few days for the whole world to know about the cool new > features you've introduced into 3.4.1. > > -- > 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: showcase your new features in Sage 3.4.1
On Sat, Apr 25, 2009 at 6:56 PM, Bill Hart wrote: > > Just wanted to thank you for the awesome job you've done on the > release tour. It's really impressive work. I personally find it very > useful. Looking at how much got added just in sage-3.4.1 is totally mind boggling (!). -- William > > Bill. > > On 26 Apr, 02:48, Minh Nguyen wrote: >> Hi folks, >> >> The release tour for Sage 3.4.1 is pretty much done now. You can find it at >> >> http://wiki.sagemath.org/sage-3.4.1 >> >> Just in case I've forgotten to showcase new features you've introduced >> in Sage 3.4.1, this is a friendly reminder for you to alert me to them >> or for you to do it yourself. The release tour will be announced in >> the next few days for the whole world to know about the cool new >> features you've introduced into 3.4.1. >> >> -- >> Regards >> Minh Van Nguyen > > > -- 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 and symbolic software design
On Sat, Apr 25, 2009 at 11:43 AM, David Joyner wrote: > > Hi: > > I just started preparing for a talk next Friday in an > NSF workshop on "Future Directions of Computaton > Research" in the "Symbolic Software Design" section. Therefore, How long is your talk? Is it at NSF (so maybe a 10-minute talk)? Or just an NSF *funded* workshop? I think you need to tell us more about this workshop. Who is the audience? > I think I should say something about the work on pynac > and how it will be replacing maxima. I tried the wiki to > see what was there on this but the wiki seems to > be down. > > Any suggestions on other references or ideas on how > to present this? I really want to present Sage in as > positive light as possible, which being accurate and succinct. > I was plannning on getting ideas from the long version of the > "White paper" William and I wrote > http://sage.math.washington.edu/home/wdj/research/oscas-nsf-white-paper12.pdf > but am more than happy to listen to other suggestions. > > - David > > > > -- 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 3.4.2.alpha0 released!
Builds from scratch fine on OSX.4 on PPC G4. I do have a couple random things which came out of it, but I assume these are known - just in case, I post them: 1. I get this error message during the Sphinx run: docstring of sage.schemes.elliptic_curves.ell_rational_field.EllipticCurve_rational_field.has_good_reduction_outside_S: 7: (ERROR/3) Unknown directive type "notes". .. notes:: Primality of elements of S is not checked, and the output is undefined if S is not a list or contains non-primes. This only tests the given model, so should only be applied to minimal models. 2. I get a lot of warnings like this during the Sphinx run: WARNING: html_favicon is not an .ico file 3. I get this - maybe something wrong in this file: sage/plot/plot3d/parametric_surface.pyx:203:20: cdef variable 'u' declared after it is used 4. During cloning, I get a lot of this: warning can't open dynamic library: libpari-gmp.dylib referenced from: /Users/.../sage-3.4.2.alpha0/local/lib/libcsage.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2) Hope it 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: Sage 3.4.2.alpha0 released!
On Apr 25, 7:30 pm, kcrisman wrote: Hi, > Builds from scratch fine on OSX.4 on PPC G4. I do have a couple > random things which came out of it, but I assume these are known - > just in case, I post them: > > 1. I get this error message during the Sphinx run: > > docstring of > sage.schemes.elliptic_curves.ell_rational_field.EllipticCurve_rational_field.has_good_reduction_outside_S: > 7: (ERROR/3) Unknown directive type "notes". > > .. notes:: > > Primality of elements of S is not checked, and the output > is undefined if S is not a list or contains non-primes. > > This only tests the given model, so should only be applied to > minimal models. I did not see this - at least the build did not stop and exit. Can anyone confirm this? > 2. I get a lot of warnings like this during the Sphinx run: > > WARNING: html_favicon is not an .ico file Pat opened a ticket and posted a patch a while ago - maybe someone wants to review it? :) > 3. I get this - maybe something wrong in this file: > > sage/plot/plot3d/parametric_surface.pyx:203:20: cdef variable 'u' > declared after it is used Hmm - no clue? Is that during the build? > 4. During cloning, I get a lot of this: > > warning can't open dynamic library: libpari-gmp.dylib referenced > from: /Users/.../sage-3.4.2.alpha0/local/lib/libcsage.dylib (checking > for undefined symbols may be affected) (No such file or directory, > errno = 2) It is an annoyance with pari which provides two versions of pari, i.e. one with and one without a statically linked gmp. Just ignore it - it never seemed to bother me enough to fix this :) > Hope it helps, > > - kcrisman Cheers, Michael --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
