[sage-devel] Sage 3.0.2.rc0 released!
Hello folks, this is 3.0.2.rc0, the likely final release of the 3.0.2 series and hopefully next to identical to the final 3.0.2. What is new? * Franco Saliola and Peter Jipsen's posets and semi-lattive patch * Robert Miller's self-orthogonal binary codes * Bjarke Hammersholt Roune's Frobby is now an optional spkg * Pbuild should now pass the doctests since #3097 has been fixed. In addition there were the usual bug fixes. Please build and doctest as usual and report any issues you see. Sources and a sage.math-only binary in the usual places: http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc0.tar http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc0-sage.math-only-x86_64-Linux.tar.gz Cheers, Michael Merged in rc0: #1762: Robert Miller, Michael Abshoff: Create optional graphviz package #2121: Robert Miller: move libecm wrapper from interfaces to libs #2519: Franco Saliola, Peter Jipsen: Add support for posets, semi-lattices, etc. to Sage #3018: Bjarke Hammersholt Roune: Integrate Frobby into Sage #3097: Gary Furnish, Michael Abshoff: pbuild: make sure the files from setup.py's scripts section are copied #3104: William Stein: pbori.pyx: Make some doctest long since it uses a lot of RAM #3112: Robert Miller: Generate self-orthogonal binary codes #3148: Francis Clarke: improved orthogonal functions #3218: Michael Abshoff: fix 64 bit OSX build support for mercurial #3219: William Stein: upgrade to gmp-4.2.2 while we wait for MPIR #3242: Robert Miller: Fix little bug in G.relabel() for G a graph #3245: Mike Hansen: provide coefficient and coefficients methods for symbolic expressions #3257: Gary Furnish: Pbuild ignores gcc specific default settings #3263: Craig Citro: typo in lseries_ell.py #3266: William Stein: Sage 3.0.2.alpha1: doctest failure in sage/server/simple/twist.py #3267: Michael Abshoff: Sage 3.0.2.alpha1: doctest failure in sage/server/support.py #3269: Jason Bandlow: Improve documentation for combinat/dyck_word.py #3270: Robert Miller: trivial 100x speedup in coding theory #3272: Craig Citro: Bug in sparse polynomials over finite fields #3273: Robert Bradshaw: extend isqrt to work for Python int's in addition to Sage integers and objects with an isqrt method #3274: Michael Abshoff: OSX: delete libpng*.la since we also nuke libpng*.dylib #3275: Craig Citro: Make SL2Z distinct --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Graph planarity
Is there any reason why John Boyer's planarity code isn't an spkg? - Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: matrices with no ring specified default to QQ if the elements are all integers
I vote for Proposal B. John On May 21, 10:02 pm, Nick Alexander <[EMAIL PROTECTED]> wrote: > > Wow! In that case I revise my viewpoint on this matter. That's > > really interesting. It is amazing how many things in Sage were > > written to make Sage easier for "random undergrads", but turn > > it to be really loved by working researchers in the trenches. > > I very rarely create MatrixSpaces explicitly, because I find the word > matrix() to be a far more powerful declaration of intent. > > Nick --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: progress on Maxima + ECL
mabshoff wrote: > Out of curiosity: Did you take today's CVS since the anon ecl CVS > trees were corrupted until about two, three hours ago? I am working with ECL built from anonymous CVS from around May 14. I haven't been able to update from CVS since then; apparently the anonymous CVS server was/is out of date. best Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Cubic to Weierstrass
I attach some Pari code which computes various things, including Nagell's algorithm, including forward and reverse transforms. Accompanying it is some test code which attempts to verify that the inverse transform does what it is supposed to, i.e. it composes with the forward transform to give the identity. In various versions of Pari, the test will fail, due to bugs in Pari, but hopefully it passes on the latest version. There's all sorts of other stuff in that file, some of which is hopelessly inefficient, but which was purpose written and did not need to be fast. Of course Nagel's algorithm should not take minutes, ever. I don't make any guarantees that this code is useful for anything, even the purpose discussed here and it comes with no warranty whatsoever, but the code is hereby released under GPL v2 or above if it proves useful to anyone. Here is a link to the code: http://sage.math.washington.edu/home/wbhart/PicardBasis.txt The functions you want are toEllipticCurve and testNagell. The function toEllipticCurve(C, P) takes as arguments a cubic curve C and a Qp-rational point on it. A stupidly naive function for finding such a point is given by the function QpPoint(C, p) where p is a prime. This function will also fail in various versions of Pari, but should be fine in the latest version. The function would have to be modified if you don't want to work with Qp, but it should be straightforward to modify it. The hard part is getting all the transformations right, and they are there. Note the line: u;v;sqrtdelta;x;y;tau;t;ud;vd;wd;Ud;Vd;Wd;U;V;W;w; at the top of the file is **absolutely essential** to the correct operation of the Nagell algorithm Bill. On 23 May, 02:44, "Bobby Moretti" <[EMAIL PROTECTED]> wrote: > Andrey, > > The bundle probably would not be of much use to you, since the > function takes as input a Sage multivariate polynomial ring element > and outputs a Sage elliptic curve over some field, when all you want > is symbolic expression in Weierstrass normal form. > > Do you have a copy of the implementation of Nagell's algorithm that > you were using? I'm curious as to what is taking so long, since there > aren't very many complicated steps; it's mostly basic arithmetic. > > -Bobby > > > > On Thu, May 22, 2008 at 1:11 PM, William Stein <[EMAIL PROTECTED]> wrote: > > Andrey, > > > Check out the hg bundle attached to this ticket: > > http://trac.sagemath.org/sage_trac/ticket/1136 > > > Bobby Moretti was implementing code for doing this transformation, but > > never finished due to a subtle bug in the transformation maps (he gets the > > right cubic but not the right maps). It's possible you'll find the above > > bundle > > useful (no clue). > > > On Thu, May 22, 2008 at 1:04 PM, Andrey Novoseltsev <[EMAIL PROTECTED]> > > wrote: > > >> I tried to convert > >> 2*x*y^2 + 2*a5*t*x*y - x^2 + (2*a4 - 8*t^3)*x - 1, > >> where a4, a5, and t are some complex parameters (which I would like to > >> keep as undetermined parameters), to Weierstrass normal form using > >> Nagell's algorithm and was not quite successful since some steps near > >> the end do not finish in a reasonable time (i.e. a few minutes). It is > >> possible that I have done some mistakes, since I didn't really tested > >> my code yet, but Jacob Lewis told me that this algorithm isn't very > >> fast anyway. > > >> As far as I can tell, Sage can do this conversion using MAGMA, but > >> only over rational field. Can anyone recommend an efficient way of > >> doing such a conversion with symbolic coefficients? Or, perhaps, it is > >> already done and I just cannot find the proper function? > > >> Thank you! > >> Andrey > > > -- > > William Stein > > Associate Professor of Mathematics > > University of Washington > >http://wstein.org > > -- > Bobby Moretti > [EMAIL PROTECTED] > > -- > Bobby Moretti > [EMAIL PROTECTED] --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
On May 23, 10:42 am, mabshoff <[EMAIL PROTECTED]> wrote: > Hello folks, > > this is 3.0.2.rc0, the likely final release of the 3.0.2 series > and hopefully next to identical to the final 3.0.2. What is new? > > * Franco Saliola and Peter Jipsen's posets and semi-lattive > patch > * Robert Miller's self-orthogonal binary codes > * Bjarke Hammersholt Roune's Frobby is now an optional spkg > * Pbuild should now pass the doctests since #3097 has been > fixed. Oops, the scripts repo is missing dsage_* due to some new oddity, i.e. [EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.0.2.final/local/ bin$ hg status ! dsage_setup.py ! dsage_worker.py [EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.0.2.final/spkg/ standard/sage_scripts-3.0.2.rc0$ ls -al dsage_* -rwxr-xr-x 1 mabshoff 1090 7479 2008-05-22 23:19 dsage_setup.py -rwxr-xr-x 1 mabshoff 1090 35459 2008-05-22 23:19 dsage_worker.py The dsage_* scripts are somehow not making it out of the spkg into local/bin. So unning "hg update -C" before running the test is required. Otherwise the DSage tests will just hang. I am hopefully fixing this issue once and for all now. Cheers, Michael > In addition there were the usual bug fixes. Please build and > doctest as usual and report any issues you see. > > Sources and a sage.math-only binary in the usual places: > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sa... > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sa... > > Cheers, > > Michael > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Graph planarity
On May 23, 12:55 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: Hi Robert, > Is there any reason why John Boyer's planarity code isn't an spkg? It was submitted as a patch and included in the library tree. Is there any specific reason it should be in its own spkg? One reason I could imagine is that people might be interested in using it in stand alone code. While we are at it: Somebody please change the license notes in the code from Apache to GPL since the code was relicensed, but that is not reflected in the actual source code. > - Robert Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Graph planarity
+1. Planarity is a mess of non Cython files that are included in the main tree and should probably be compiled as a library. On Fri, May 23, 2008 at 9:05 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > On May 23, 12:55 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: > > Hi Robert, > >> Is there any reason why John Boyer's planarity code isn't an spkg? > > It was submitted as a patch and included in the library tree. Is there > any specific reason it should be in its own spkg? One reason I could > imagine is that people might be interested in using it in stand alone > code. > > While we are at it: Somebody please change the license notes in the > code from Apache to GPL since the code was relicensed, but that is not > reflected in the actual source code. > >> - Robert > > Cheers, > > Michael > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
Michael, I just built rc0 and will test it -- but where should I be when I type "hg update -C" ? John 2008/5/23 mabshoff <[EMAIL PROTECTED]>: > > > > On May 23, 10:42 am, mabshoff <[EMAIL PROTECTED]> wrote: >> Hello folks, >> >> this is 3.0.2.rc0, the likely final release of the 3.0.2 series >> and hopefully next to identical to the final 3.0.2. What is new? >> >> * Franco Saliola and Peter Jipsen's posets and semi-lattive >>patch >> * Robert Miller's self-orthogonal binary codes >> * Bjarke Hammersholt Roune's Frobby is now an optional spkg >> * Pbuild should now pass the doctests since #3097 has been >>fixed. > > Oops, the scripts repo is missing dsage_* due to some new oddity, i.e. > > [EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.0.2.final/local/ > bin$ hg status > ! dsage_setup.py > ! dsage_worker.py > [EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.0.2.final/spkg/ > standard/sage_scripts-3.0.2.rc0$ ls -al dsage_* > -rwxr-xr-x 1 mabshoff 1090 7479 2008-05-22 23:19 dsage_setup.py > -rwxr-xr-x 1 mabshoff 1090 35459 2008-05-22 23:19 dsage_worker.py > > The dsage_* scripts are somehow not making it out of the spkg into > local/bin. So unning "hg update -C" before running the test is > required. Otherwise the DSage tests will just hang. > > I am hopefully fixing this issue once and for all now. > > Cheers, > > Michael > >> In addition there were the usual bug fixes. Please build and >> doctest as usual and report any issues you see. >> >> Sources and a sage.math-only binary in the usual places: >> >> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sa... >> >> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sa... >> >> Cheers, >> >> Michael >> > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
On May 23, 5:28 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > Michael, > > I just built rc0 and will test it -- but where should I be when I type > "hg update -C" ? > > John Hi John, that is in $SAGE_ROOT/local/bin after sourcing local/bin/sage_env from $SAGE_ROOT. Before runnign "hg update -C" it should look like sage-3.0.2.final/local/bin$ hg status ! dsage_setup.py ! dsage_worker.py afterwars "hg status" should just show an unchanged repo without any missing files. 3.0.2.rc1 is coming up. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
Thanks, that worked as advertised. I'm doing --testall on rc0 anyway now. John 2008/5/23 mabshoff <[EMAIL PROTECTED]>: > > > > On May 23, 5:28 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: >> Michael, >> >> I just built rc0 and will test it -- but where should I be when I type >> "hg update -C" ? >> >> John > > Hi John, > > that is in $SAGE_ROOT/local/bin after sourcing local/bin/sage_env from > $SAGE_ROOT. Before runnign "hg update -C" it should look like > > sage-3.0.2.final/local/bin$ hg status > ! dsage_setup.py > ! dsage_worker.py > > afterwars "hg status" should just show an unchanged repo without any > missing files. 3.0.2.rc1 is coming up. > > Cheers, > > Michael > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
Builds fine on an amd phenom machine running hardy heron but sage -testall freezes at sage -t devel/sage/sage/dsage/__init__.py (skipping) -- nodoctest.py file in directory sage -t devel/sage/sage/dsage/tests/testdoc.py + On Fri, May 23, 2008 at 4:42 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > this is 3.0.2.rc0, the likely final release of the 3.0.2 series > and hopefully next to identical to the final 3.0.2. What is new? > > * Franco Saliola and Peter Jipsen's posets and semi-lattive > patch > * Robert Miller's self-orthogonal binary codes > * Bjarke Hammersholt Roune's Frobby is now an optional spkg > * Pbuild should now pass the doctests since #3097 has been > fixed. > > In addition there were the usual bug fixes. Please build and > doctest as usual and report any issues you see. > > Sources and a sage.math-only binary in the usual places: > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc0.tar > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc0-sage.math-only-x86_64-Linux.tar.gz > > Cheers, > > Michael > > > Merged in rc0: > > #1762: Robert Miller, Michael Abshoff: Create optional graphviz > package > #2121: Robert Miller: move libecm wrapper from interfaces to libs > #2519: Franco Saliola, Peter Jipsen: Add support for posets, > semi-lattices, etc. to Sage > #3018: Bjarke Hammersholt Roune: Integrate Frobby into Sage > #3097: Gary Furnish, Michael Abshoff: pbuild: make sure the files > from setup.py's scripts section are copied > #3104: William Stein: pbori.pyx: Make some doctest long since > it uses a lot of RAM > #3112: Robert Miller: Generate self-orthogonal binary codes > #3148: Francis Clarke: improved orthogonal functions > #3218: Michael Abshoff: fix 64 bit OSX build support for mercurial > #3219: William Stein: upgrade to gmp-4.2.2 while we wait for MPIR > #3242: Robert Miller: Fix little bug in G.relabel() for G a graph > #3245: Mike Hansen: provide coefficient and coefficients methods > for symbolic expressions > #3257: Gary Furnish: Pbuild ignores gcc specific default settings > #3263: Craig Citro: typo in lseries_ell.py > #3266: William Stein: Sage 3.0.2.alpha1: doctest failure in > sage/server/simple/twist.py > #3267: Michael Abshoff: Sage 3.0.2.alpha1: doctest failure in > sage/server/support.py > #3269: Jason Bandlow: Improve documentation for combinat/dyck_word.py > #3270: Robert Miller: trivial 100x speedup in coding theory > #3272: Craig Citro: Bug in sparse polynomials over finite fields > #3273: Robert Bradshaw: extend isqrt to work for Python int's in > addition to Sage integers and objects with an isqrt method > #3274: Michael Abshoff: OSX: delete libpng*.la since we also nuke > libpng*.dylib > #3275: Craig Citro: Make SL2Z distinct > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
On May 23, 6:09 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > Builds fine on an amd phenom machine running hardy heron but sage -testall > freezes at > > sage -t devel/sage/sage/dsage/__init__.py (skipping) -- nodoctest.py > file in directory > sage -t devel/sage/sage/dsage/tests/testdoc.py Hi David, the is the same issue I mentioned above. The fix is also described in a previous email. 3.0.2.rc1 will have the fix from #3279 applied. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: matrices with no ring specified default to QQ if the elements are all integers
For what it's worth, I prefer B. Michel On May 23, 3:17 pm, John Cremona <[EMAIL PROTECTED]> wrote: > I vote for Proposal B. > > John > > On May 21, 10:02 pm, Nick Alexander <[EMAIL PROTECTED]> wrote: > > > > Wow! In that case I revise my viewpoint on this matter. That's > > > really interesting. It is amazing how many things in Sage were > > > written to make Sage easier for "random undergrads", but turn > > > it to be really loved by working researchers in the trenches. > > > I very rarely create MatrixSpaces explicitly, because I find the word > > matrix() to be a far more powerful declaration of intent. > > > Nick --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: matrices with no ring specified default to QQ if the elements are all integers
Jason Grout wrote: > In the recent discussion "Change the default base_ring for matrices from > ZZ to QQ", there were lots of opinions shared, and William summarized > some feelings from the group, but it wasn't a solid conclusion (at > least, based on an IRC conversation, William is rethinking the conclusion). > > Here are two (somewhat competing) proposals, one from an IRC discussion > with William just now and the other from William's summary from the > previous thread. > > Proposal A: > > If a ring is not specified in a matrix() call, and the elements provided > are all integers (or if there are no elements provided), then the base > ring would default to QQ (instead of ZZ, as would currently happen). > > Reasons (from William and from discussions with a linear algebra person): > > 1. "linear algebra" is over fields (as opposed to module theory). When > commonly-created matrices (i.e., ones with integer entries or with no > specified entries) "default" to non-fields, the behavior is very > surprising to linear algebra people and casual users (like linear > algebra students, for example). > > 2. the matrix() command was designed for ease of use for "casual end users" > > 3. It is very easy to explicitly specify a ring, either in matrix() or > via MatrixSpace > > > So here are the cases we would see a change in behavior > > matrix(3,3) would return a 3x3 zero matrix over QQ instead of over ZZ > > matrix(3,range(9)) would return a 3x3 matrix over QQ instead of over ZZ. > > > Proposal B (from William's summary on the previous thread): > > Leave matrix() as-is. Rename echelon_form to hermite_form, and make a > new echelon_form function that computes hermite_form over the fraction > field of the base ring. It sounds like the popular vote selects proposal B. This is being tracked at #3211. Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
All tests passed! with rc0 + the dsage fix manually applied. John 2008/5/23 mabshoff <[EMAIL PROTECTED]>: > > > > On May 23, 6:09 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: >> Builds fine on an amd phenom machine running hardy heron but sage -testall >> freezes at >> >> sage -t devel/sage/sage/dsage/__init__.py (skipping) -- nodoctest.py >> file in directory >> sage -t devel/sage/sage/dsage/tests/testdoc.py > > Hi David, > > the is the same issue I mentioned above. The fix is also described in > a previous email. 3.0.2.rc1 will have the fix from #3279 applied. > > Cheers, > > Michael > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Trac #1284
Hello, During the last bug day, I found several tickets related to inconsistencies in abelian groups. I think I've fixed the circular logic, etc. causing the problems in the patch included in #1284. However, there is a difference of opinion on notation that I need to ask about here. Q: Should the output of sage: G <= H for G and H abelian groups be whether G is a subgroup of H? I know the answer seems simple, but here's why you might want to answer no (William suggested this to me). If you have a list of abelian groups L = [G1,...,Gn], and you want to quickly sort it, if you do sorted(L), you may not get back what you are expecting, since the subgroup ordering on abelian groups isn't linear. gfurnish proposes the alternative sorted(L, cmp=canonical_ab_group_cmp), with G <= H returning whether G is a subgroup of H. I think I favor this approach. The other option is G.is_subgroup(H). --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Trac #1284
> Q: Should the output of > sage: G <= H > for G and H abelian groups be whether G is a subgroup of H? I say yes, this is a useful notation. > If you have a list of > abelian groups L = [G1,...,Gn], and you want to quickly sort it What is a "sorted list of groups"? Sorted by what? If the user doesn't realize that this is nonsense there are bigger problems. Nick --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Trac #1284
We should maintain consistency with other algebraic structures. If G<=H means "G is a subgroup of H" when G and H are groups, then I would similarly expect <= to mean "is a subspace of" for vector spaces, etc. Some of these cases might be hard (number fields?); so if the functionality is not (yet) implemented for a similar type, a reasonable NotImplementedError should occur. I'll try reviewing the patch itself now... John On May 23, 5:45 pm, Robert Miller <[EMAIL PROTECTED]> wrote: > Hello, > > During the last bug day, I found several tickets related to > inconsistencies in abelian groups. I think I've fixed the circular > logic, etc. causing the problems in the patch included in #1284. > However, there is a difference of opinion on notation that I need to > ask about here. > > Q: Should the output of > sage: G <= H > for G and H abelian groups be whether G is a subgroup of H? > > I know the answer seems simple, but here's why you might want to > answer no (William suggested this to me). If you have a list of > abelian groups L = [G1,...,Gn], and you want to quickly sort it, if > you do sorted(L), you may not get back what you are expecting, since > the subgroup ordering on abelian groups isn't linear. > > gfurnish proposes the alternative sorted(L, > cmp=canonical_ab_group_cmp), with G <= H returning whether G is a > subgroup of H. I think I favor this approach. > > The other option is G.is_subgroup(H). --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Trac #1284
I agree with Nick and John. On Fri, May 23, 2008 at 12:45 PM, Robert Miller <[EMAIL PROTECTED]> wrote: > > Hello, > > During the last bug day, I found several tickets related to > inconsistencies in abelian groups. I think I've fixed the circular > logic, etc. causing the problems in the patch included in #1284. > However, there is a difference of opinion on notation that I need to > ask about here. > > Q: Should the output of > sage: G <= H > for G and H abelian groups be whether G is a subgroup of H? > > I know the answer seems simple, but here's why you might want to > answer no (William suggested this to me). If you have a list of > abelian groups L = [G1,...,Gn], and you want to quickly sort it, if > you do sorted(L), you may not get back what you are expecting, since > the subgroup ordering on abelian groups isn't linear. > > gfurnish proposes the alternative sorted(L, > cmp=canonical_ab_group_cmp), with G <= H returning whether G is a > subgroup of H. I think I favor this approach. > > The other option is G.is_subgroup(H). > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > All tests passed! with rc0 + the dsage fix manually applied. > > John Cool, I have released http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar which fixes three issues: #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the scrips.spkg #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation issues #3281: Gary Furnish: libecm fails to pbuild I verified with a fresh build that #3279 is truly fixed, so let's hope for the best. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Trac #3276 + Maxima-isms
With the symbolics rewrite moving quickly, I'd like to request that if possible people try to avoid adding more "Maxima-isms" to sage.calculus. Specifically, if functionality is being added, please try to keep it "general" in that the design of the functionality is not dictated by what Maxima does. Functions that pass arguments directly to Maxima are especially bad, as I either have to break API compatibility or write complicated, expensive (to write and to execute) parsers to allow backwards compatibility, and I'm not a very big fan of having to remove interfaces that were added less then a month before. This applies primarily to things like assume(x, "analytic") or otherwise where we are just passing a symbolic expression directly to Maxima without any real internal logic (which is also bad because it means the code isn't really doing any error checking either). Thanks, Gary --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: matrices with no ring specified default to QQ if the elements are all integers
On Fri, May 23, 2008 at 9:40 AM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Jason Grout wrote: >> In the recent discussion "Change the default base_ring for matrices from >> ZZ to QQ", there were lots of opinions shared, and William summarized >> some feelings from the group, but it wasn't a solid conclusion (at >> least, based on an IRC conversation, William is rethinking the conclusion). >> >> Here are two (somewhat competing) proposals, one from an IRC discussion >> with William just now and the other from William's summary from the >> previous thread. >> >> Proposal A: >> >> If a ring is not specified in a matrix() call, and the elements provided >> are all integers (or if there are no elements provided), then the base >> ring would default to QQ (instead of ZZ, as would currently happen). >> >> Reasons (from William and from discussions with a linear algebra person): >> >> 1. "linear algebra" is over fields (as opposed to module theory). When >> commonly-created matrices (i.e., ones with integer entries or with no >> specified entries) "default" to non-fields, the behavior is very >> surprising to linear algebra people and casual users (like linear >> algebra students, for example). >> >> 2. the matrix() command was designed for ease of use for "casual end users" >> >> 3. It is very easy to explicitly specify a ring, either in matrix() or >> via MatrixSpace >> >> >> So here are the cases we would see a change in behavior >> >> matrix(3,3) would return a 3x3 zero matrix over QQ instead of over ZZ >> >> matrix(3,range(9)) would return a 3x3 matrix over QQ instead of over ZZ. >> >> >> Proposal B (from William's summary on the previous thread): >> >> Leave matrix() as-is. Rename echelon_form to hermite_form, and make a >> new echelon_form function that computes hermite_form over the fraction >> field of the base ring. > > > It sounds like the popular vote selects proposal B. This is being > tracked at #3211. > As BDFL (and person who supported A instead of B overall), and now agree that by popular vote we should do B. -- William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Trac #1284
Following on from Nick's point, I cannot imagine that users will want or expect to sort a list of groups except possibly by some criterion provided by the user (e.g. size of the group, or something). But apart from that we need to be able to have a default sorting or more or less anything in Sage so that we can have consistent output where possible and meaningful. John 2008/5/23 David Joyner <[EMAIL PROTECTED]>: > > I agree with Nick and John. > > On Fri, May 23, 2008 at 12:45 PM, Robert Miller <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> During the last bug day, I found several tickets related to >> inconsistencies in abelian groups. I think I've fixed the circular >> logic, etc. causing the problems in the patch included in #1284. >> However, there is a difference of opinion on notation that I need to >> ask about here. >> >> Q: Should the output of >> sage: G <= H >> for G and H abelian groups be whether G is a subgroup of H? >> >> I know the answer seems simple, but here's why you might want to >> answer no (William suggested this to me). If you have a list of >> abelian groups L = [G1,...,Gn], and you want to quickly sort it, if >> you do sorted(L), you may not get back what you are expecting, since >> the subgroup ordering on abelian groups isn't linear. >> >> gfurnish proposes the alternative sorted(L, >> cmp=canonical_ab_group_cmp), with G <= H returning whether G is a >> subgroup of H. I think I favor this approach. >> >> The other option is G.is_subgroup(H). >> > >> > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: raw picture manipulation [gd library and sage?]
What I'm doing is very simple. I've written a wrapper for the gd library, which allows me direct and *unsafe* access to the image data. All I have right now is functions to fetch a matrix from the red, green, and blue channels to a matrix, and dump data from matrices into said channels. Eventually, this will be a more-or-less feature-complete gd wrapper, so you'll be able to draw lines, arcs, text, etc. For the application of image<-->matrix, this is a *vast* improvement over gdmodule (the Python API wrap of gd), since the best it offers is python functions to set and read pixels one at a time. In my version, I never do anything with python in my inner loops. This makes things super speedy (say, a few hundred times faster). That said, my default "error handling" is nonexistent, which is to say, I segfault like it's going out of style. I haven't had time to work on this because I'm busy with other projects (F4 and my senior thesis). You'll probably see something by the end of dev1, since Marshall Hampton has agreed to help me get this up & running. --tom On Fri, 23 May 2008, David Joyner wrote: > Hi Tom: > > I heard you are working on image processing stuff and was wondering if > it would be > possible to get a rough idea of what you are doing. I just want to be > able to try to > follow along, if possible. I doubt I can help beyond testing and > encouragement though. > I'm having a lot of fun reading Alasdair McAndrew's Into to Digital Processing > (FYI, which I think is <$10 used on amazon.com!). > > - David > > On Fri, May 23, 2008 at 2:25 PM, Marshall Hampton <[EMAIL PROTECTED]> wrote: >> >> Tom Boothby, who I think does not read this list, is also working on >> improving image manipulation in sage without using the PIL. He is >> only using the gd library. Its a work in progress right now though. >> >> -M. Hampton >> >> On May 23, 9:26 am, Simon King <[EMAIL PROTECTED]> wrote: >>> Dear Jason, dear David, >>> >>> On May 23, 3:57 pm, Jason Grout <[EMAIL PROTECTED]> wrote:> David Joyner >>> wrote: Since it's come up several times, it might be worth material for inclusion in the FAQ. > Since PIL has come up a few times on SAGE lists in vague ways, I > thought I'd try to > be more detailed. Here is a way using SAGE which might help. First, > it requires some preparation. >>> ... > You must install PIL fromhttp://www.pythonware.com/products/pil/. Here's > how: >>> >>> ... >>> >>> There is an experimental package PIL-1.1.5.spkg. This Tuesday i >>> succeeded to install it (on SUSE linux) simply with >>> sage -i PIL-1.1.5.spkg >>> after installing xv (and after installing mpi4py-0.3.1.spkg and >>> openmpi-1.1.4.spkg, i don't know if this is related). >>> >>> Perhaps this is easier than the way you described (however i don't >>> know whether "experimental" means that it wouldn't work on all >>> platforms) >>> >>> Yours >>> Simon >> >> >> > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Trac #1284
I expect <= to be a total order, so I prefer is_subgroup. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Trac #1284
I agree, which is why I supported making some sort of canonical_comparison method for output, and then using <= for subgroup. On Fri, May 23, 2008 at 11:36 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > Following on from Nick's point, I cannot imagine that users will want > or expect to sort a list of groups except possibly by some criterion > provided by the user (e.g. size of the group, or something). But > apart from that we need to be able to have a default sorting or more > or less anything in Sage so that we can have consistent output where > possible and meaningful. > > John > > 2008/5/23 David Joyner <[EMAIL PROTECTED]>: >> >> I agree with Nick and John. >> >> On Fri, May 23, 2008 at 12:45 PM, Robert Miller <[EMAIL PROTECTED]> wrote: >>> >>> Hello, >>> >>> During the last bug day, I found several tickets related to >>> inconsistencies in abelian groups. I think I've fixed the circular >>> logic, etc. causing the problems in the patch included in #1284. >>> However, there is a difference of opinion on notation that I need to >>> ask about here. >>> >>> Q: Should the output of >>> sage: G <= H >>> for G and H abelian groups be whether G is a subgroup of H? >>> >>> I know the answer seems simple, but here's why you might want to >>> answer no (William suggested this to me). If you have a list of >>> abelian groups L = [G1,...,Gn], and you want to quickly sort it, if >>> you do sorted(L), you may not get back what you are expecting, since >>> the subgroup ordering on abelian groups isn't linear. >>> >>> gfurnish proposes the alternative sorted(L, >>> cmp=canonical_ab_group_cmp), with G <= H returning whether G is a >>> subgroup of H. I think I favor this approach. >>> >>> The other option is G.is_subgroup(H). >>> > >>> >> >> > >> > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
Everything builds and tests ok out of the box for me with rc2: All tests passed! Total time for all tests: 2622.9 seconds Please see /home/jec/sage-3.0.2.rc2/tmp/test.log for the complete log from this test. John 2008/5/23 mabshoff <[EMAIL PROTECTED]>: > > > > On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: >> All tests passed! with rc0 + the dsage fix manually applied. >> >> John > > Cool, I have released > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar > > which fixes three issues: > > #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the > scrips.spkg > #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation > issues > #3281: Gary Furnish: libecm fails to pbuild > > I verified with a fresh build that #3279 is truly fixed, so let's hope > for the best. > > Cheers, > > Michael > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
mabshoff wrote: > > > On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: >> All tests passed! with rc0 + the dsage fix manually applied. >> >> John > > Cool, I have released > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar > > which fixes three issues: > > #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the > scrips.spkg > #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation > issues > #3281: Gary Furnish: libecm fails to pbuild > > I verified with a fresh build that #3279 is truly fixed, so let's hope > for the best. > pbuild did it on Fedora 9, 32 bits with 2 cpu's. Now testing. Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
Jaap Spies wrote: > mabshoff wrote: >> >> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: >>> All tests passed! with rc0 + the dsage fix manually applied. >>> >>> John >> Cool, I have released >> >> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar >> >> which fixes three issues: >> >> #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the >> scrips.spkg >> #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation >> issues >> #3281: Gary Furnish: libecm fails to pbuild >> >> I verified with a fresh build that #3279 is truly fixed, so let's hope >> for the best. >> > > pbuild did it on Fedora 9, 32 bits with 2 cpu's. > Now testing. > Forget this. .sage did not run: ImportError: /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python2.5/site-packages/sage/libs/mwrank/mwrank.so: undefined symbol: mw_del sage: Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
Jaap Spies wrote: > mabshoff wrote: >> >> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: >>> All tests passed! with rc0 + the dsage fix manually applied. >>> >>> John >> Cool, I have released >> >> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar >> >> which fixes three issues: >> >> #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the >> scrips.spkg >> #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation >> issues >> #3281: Gary Furnish: libecm fails to pbuild >> >> I verified with a fresh build that #3279 is truly fixed, so let's hope >> for the best. >> > > pbuild did it on Fedora 9, 32 bits with 2 cpu's. > Now testing. > [EMAIL PROTECTED] sage-3.0.2.rc2]$ ./sage -- | SAGE Version 3.0.2.rc2, Release Date: 2008-05-23 | | Type notebook() for the GUI, and license() for information.| -- --- ImportError Traceback (most recent call last) /home/jaap/work/downloads/sage-3.0.2.rc2/local/bin/ in () /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/all_cmdline.py in () 12 try: 13 ---> 14 from sage.all import * 15 from sage.calculus.predefined import x 16 preparser(on=True) /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/all.py in () 60 from sage.misc.sh import sh 61 ---> 62 from sage.libs.all import * 63 64 get_sigs() /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/libs/all.py in () 10 from sage.libs.pari.all import pari, pari_gen, allocatemem, PariError 11 ---> 12 from sage.libs.mwrank.all import (mwrank_EllipticCurve, mwrank_MordellWeil, 13mwrank_initprimes, 14set_precision as mwrank_set_precision) /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/libs/mwrank/all.py in () 8set_precision) 9 ---> 10 from mwrank import initprimes as mwrank_initprimes 11 12 ImportError: /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python2.5/site-packages/sage/libs/mwrank/mwrank.so: undefined symbol: mw_del sage: 1+1 --- NameError Traceback (most recent call last) /home/jaap/work/downloads/sage-3.0.2.rc2/local/bin/ in () NameError: name 'Integer' is not defined sage: Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Graph planarity
> While we are at it: Somebody please change the license notes in the > code from Apache to GPL since the code was relicensed, but that is not > reflected in the actual source code. > Actually, it is not released under GPL. It's currently licensed under Apache 2.0, which is GPL compatible. It had previously been under Boyer's personal license. --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Graph planarity
> Actually, it is not released under GPL. It's currently licensed under > Apache 2.0, which is GPL compatible. It had previously been under > Boyer's personal license. The Apache 2.0 license is not compatible with GPLv2. I believe during Sage Days 7, he released it (at least to Sage) under the GPL. --Mike --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
On Fri, May 23, 2008 at 1:16 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: >> All tests passed! with rc0 + the dsage fix manually applied. >> >> John > > Cool, I have released > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar Builds fine and all tests passed on amd phenom hardy heron. > > which fixes three issues: > > #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the > scrips.spkg > #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation > issues > #3281: Gary Furnish: libecm fails to pbuild > > I verified with a fresh build that #3279 is truly fixed, so let's hope > for the best. > > Cheers, > > Michael > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Graph planarity
On Fri, May 23, 2008 at 4:02 PM, Mike Hansen <[EMAIL PROTECTED]> wrote: > >> Actually, it is not released under GPL. It's currently licensed under >> Apache 2.0, which is GPL compatible. It had previously been under >> Boyer's personal license. > > The Apache 2.0 license is not compatible with GPLv2. I believe during > Sage Days 7, he released it (at least to Sage) under the GPL. > I think apache 2.0 is not GPLv2 compatible, but Apache 2.0 *is* GPLv2+ compatible. William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Graph planarity
On Fri, May 23, 2008 at 4:43 PM, William Stein <[EMAIL PROTECTED]> wrote: > On Fri, May 23, 2008 at 4:02 PM, Mike Hansen <[EMAIL PROTECTED]> wrote: >> >>> Actually, it is not released under GPL. It's currently licensed under >>> Apache 2.0, which is GPL compatible. It had previously been under >>> Boyer's personal license. >> >> The Apache 2.0 license is not compatible with GPLv2. I believe during >> Sage Days 7, he released it (at least to Sage) under the GPL. >> > > I think apache 2.0 is not GPLv2 compatible, but Apache 2.0 *is* GPLv2+ > compatible. > I just talked about this with Michael, and we really don't want Apache code linked into Sage, at least not for our Microsoft Windows port. Emily, Robert, and Jon Bober - could you guys get documentation that the code has been relicensed GPLv2 and change the headers, or if not please contact the author? -- William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.2.rc0 released!
#3291 fixes this issue and will be merged in RC3/Release in case anyone else is having this iissue On Fri, May 23, 2008 at 3:56 PM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > Jaap Spies wrote: >> mabshoff wrote: >>> >>> On May 23, 6:44 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: All tests passed! with rc0 + the dsage fix manually applied. John >>> Cool, I have released >>> >>> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc2.tar >>> >>> which fixes three issues: >>> >>> #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the >>> scrips.spkg >>> #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation >>> issues >>> #3281: Gary Furnish: libecm fails to pbuild >>> >>> I verified with a fresh build that #3279 is truly fixed, so let's hope >>> for the best. >>> >> >> pbuild did it on Fedora 9, 32 bits with 2 cpu's. >> Now testing. >> > > [EMAIL PROTECTED] sage-3.0.2.rc2]$ ./sage > -- > | SAGE Version 3.0.2.rc2, Release Date: 2008-05-23 | > | Type notebook() for the GUI, and license() for information.| > -- > > --- > ImportError Traceback (most recent call last) > > /home/jaap/work/downloads/sage-3.0.2.rc2/local/bin/ in > () > > /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/all_cmdline.py > in () > 12 try: > 13 > ---> 14 from sage.all import * > 15 from sage.calculus.predefined import x > 16 preparser(on=True) > > /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/all.py > in () > 60 from sage.misc.sh import sh > 61 > ---> 62 from sage.libs.all import * > 63 > 64 get_sigs() > > /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/libs/all.py > in () > 10 from sage.libs.pari.all import pari, pari_gen, allocatemem, > PariError > 11 > ---> 12 from sage.libs.mwrank.all import (mwrank_EllipticCurve, > mwrank_MordellWeil, > 13mwrank_initprimes, > 14set_precision as > mwrank_set_precision) > > /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python/site-packages/sage/libs/mwrank/all.py > in () > 8set_precision) > 9 > ---> 10 from mwrank import initprimes as mwrank_initprimes > 11 > 12 > > ImportError: > /home/jaap/downloads/sage-3.0.2.rc2/local/lib/python2.5/site-packages/sage/libs/mwrank/mwrank.so: > undefined symbol: mw_del > > sage: 1+1 > --- > NameError Traceback (most recent call last) > > /home/jaap/work/downloads/sage-3.0.2.rc2/local/bin/ in > () > > NameError: name 'Integer' is not defined > > sage: > > > > Jaap > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Sage 3.0.2.rc3 released!
Hello folks, here we go with 3.0.2.rc3. It is basically a bunch of bug fixes for rlm's codes code that had a couple small issues left ;) In addition there is one pbuild issue fix that Jaap encountered and that in the past was also hit by David Joyner. Sources are at http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0.2/sage-3.0.2.rc3.tar Unless something goes horribly wrong this will be identical to the final 3.0.2 release. If you added some feature that should be in the Sage release tour please add them to http://wiki.sagemath.org/sage-3.0.2 Right now that list consists of * Franco Saliola and Peter Jipsen's posets and semi-lattive patch * Robert Miller's self-orthogonal binary codes * Bjarke Hammersholt Roune's Frobby is now an optional spkg But feel free to add items. As usual please test and report *any* issue you hit. Cheers, Michael Merged in rc3: #3285: Robert Miller: segfault in binary_code.pyx on 32-bit linux #3287: William Stein: worksheet.py -- doctest failure blocking a release #3288: Robert Miller: linear_code -- memory errors in doctests on Arch Linux #3289: Robert Miller: linear_code -- segfaults on ubuntu linux #3291: Gary Furnish: pbuild doesn't properly compile mwrank.so on some systems Merged in rc1/2: #3279: Michael Abshoff: Sage 3.0.2.rc0: Copy dsage_* scripts from the scrips.spkg #3280: Michael Abshoff: Sage 3.0.2.rc0: fix rebuild Sage documentation issues #3281: Gary Furnish: libecm fails to pbuild --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel]
Does anyone else find the printing of 0 below inconsistent? sage: CC(0) 0 sage: RR(0) 0.000 sage: CC Complex Field with 53 bits of precision sage: RR Real Field with 53 bits of precision It doesn't always happen: sage: RR(2) 2.00 sage: CC(2) 2.00 sage: version() # heavily modified but not in the printing code :) 'SAGE Version 3.0.1.alpha0, Release Date: 2008-04-26' Nick --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: [sage-devel]
On Fri, May 23, 2008 at 10:18 PM, Nick Alexander <[EMAIL PROTECTED]> wrote: > > Does anyone else find the printing of 0 below inconsistent? > > sage: CC(0) > 0 > sage: RR(0) > 0.000 Yes, I agree that this is inconsistent and should be changed. Probably the right change would be: sage: CC(0) 0.000 I'm very curious if Carl Witty has any comments. William > sage: CC > Complex Field with 53 bits of precision > sage: RR > Real Field with 53 bits of precision > > It doesn't always happen: > sage: RR(2) > 2.00 > sage: CC(2) > 2.00 > > sage: version() # heavily modified but not in the printing code :) > 'SAGE Version 3.0.1.alpha0, Release Date: 2008-04-26' > > Nick > > > > -- 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
