[sage-devel] Sage 4.1.2.alpha2 doctest failures on x86 openSUSE 11.0
Hi folks, Compiling Sage 4.1.2.alpha2 from scratch went OK on 32-bit openSUSE 11.0. Here are the doctest failures on that platform: ** doctest failures on 32-bit openSUSE 11.0 ** sage -t -long "devel/sage/sage/rings/polynomial/pbori.pyx" ** File "/data/students/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx", line 3940: sage: x.stable_hash() Expected: 173100285919 Got: -845955105 ** File "/data/students/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx", line 4849: sage: s.stable_hash() Expected: 173100285919 Got: -845955105 ** File "/data/students/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx", line 1976: sage: m.stable_hash() Expected: 173100285919 Got: -845955105 ** 3 items had failures: 1 of 4 in __main__.example_128 1 of 5 in __main__.example_165 1 of 5 in __main__.example_48 ***Test Failed*** 3 failures. For whitespace errors, see the file /student/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/tmp/.doctest_pbori.py [4.4 s] sage -t -long "devel/sage/sage/crypto/boolean_function.pyx" ** File "/data/students/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/devel/sage/sage/crypto/boolean_function.pyx", line 1013: sage: B.nonlinearity() Expected: 222 Got: 217 ** 1 items had failures: 1 of 6 in __main__.example_36 ***Test Failed*** 1 failures. For whitespace errors, see the file /student/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/tmp/.doctest_boolean_function.py [3.5 s] sage -t -long "devel/sage/sage/interfaces/gp.py" ** File "/data/students/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/devel/sage/sage/interfaces/gp.py", line 567: sage: repr(gp(10.^80)).replace(gp._exponent_symbol(), 'e') Expected nothing Got: '1.000e80' ** 1 items had failures: 1 of 4 in __main__.example_26 ***Test Failed*** 1 failures. For whitespace errors, see the file /student/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/tmp/.doctest_gp.py [2.7 s] sage -t -long "devel/sage/sage/interfaces/expect.py" ** File "/data/students/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/devel/sage/sage/interfaces/expect.py", line 1599: sage: gp(10.^80)._sage_repr() Expected nothing Got: '1.000e80' ** 1 items had failures: 1 of 3 in __main__.example_45 ***Test Failed*** 1 failures. For whitespace errors, see the file /student/pg/s3599415/scratch/upgrade-farm/sage-4.1.2.alpha2/tmp/.doctest_expect.py [12.0 s] -- The following tests failed: sage -t -long "devel/sage/sage/rings/polynomial/pbori.pyx" sage -t -long "devel/sage/sage/crypto/boolean_function.pyx" sage -t -long "devel/sage/sage/interfaces/gp.py" sage -t -long "devel/sage/sage/interfaces/expect.py" Total time for all tests: 6701.6 seconds These are exactly the same failures as those reported at sage-devel [1] for 32-bit OS X 10.5.8 on bsd.math. [1] http://groups.google.com/group/sage-devel/browse_thread/thread/954ecbadeb7676a8 -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.2.alpha2 released
Hi John, On Tue, Sep 22, 2009 at 12:20 PM, John H Palmieri wrote: > On sage.math, using the prebuilt binary, I'm getting a ton of errors, > mostly of the sort > >TypeError: Unable to start maxima Using the sage.math binary for Sage 4.1.2.alpha1 [1], upgrading that to Sage 4.1.2.alpha2 results in dozens of doctest failures: -- The following tests failed: sage -t -long "devel/sage/doc/en/tutorial/interfaces.rst" sage -t -long "devel/sage/doc/en/tutorial/tour_algebra.rst" sage -t -long "devel/sage/doc/en/constructions/plotting.rst" sage -t -long "devel/sage/doc/en/constructions/interface_issues.rst" sage -t -long "devel/sage/doc/en/constructions/polynomials.rst" sage -t -long "devel/sage/doc/en/constructions/linear_algebra.rst" sage -t -long "devel/sage/doc/en/constructions/calculus.rst" sage -t -long "devel/sage/doc/en/bordeaux_2008/nf_introduction.rst" sage -t -long "devel/sage/doc/en/a_tour_of_sage/index.rst" sage -t -long "devel/sage/doc/fr/tutorial/interfaces.rst" sage -t -long "devel/sage/doc/fr/tutorial/tour_algebra.rst" sage -t -long "devel/sage/sage/modular/overconvergent/genus0.py" sage -t -long "devel/sage/sage/modular/overconvergent/weightspace.py" sage -t -long "devel/sage/sage/misc/latex.py" sage -t -long "devel/sage/sage/misc/functional.py" sage -t -long "devel/sage/sage/misc/citation.pyx" sage -t -long "devel/sage/sage/modules/vector_real_double_dense.pyx" sage -t -long "devel/sage/sage/matrix/matrix_symbolic_dense.pyx" sage -t -long "devel/sage/sage/matrix/matrix2.pyx" sage -t -long "devel/sage/sage/matrix/matrix1.pyx" sage -t -long "devel/sage/sage/rings/contfrac.py" sage -t -long "devel/sage/sage/rings/number_field/number_field_element_quadratic.pyx" sage -t -long "devel/sage/sage/rings/number_field/number_field_element.pyx" sage -t -long "devel/sage/sage/rings/polynomial/polynomial_element.pyx" sage -t -long "devel/sage/sage/tests/benchmark.py" sage -t -long "devel/sage/sage/structure/parent.pyx" sage -t -long "devel/sage/sage/structure/sage_object.pyx" sage -t -long "devel/sage/sage/gsl/interpolation.pyx" sage -t -long "devel/sage/sage/gsl/integration.pyx" sage -t -long "devel/sage/sage/combinat/combinat.py" sage -t -long "devel/sage/sage/geometry/lattice_polytope.py" sage -t -long "devel/sage/sage/calculus/desolvers.py" sage -t -long "devel/sage/sage/calculus/calculus.py" sage -t -long "devel/sage/sage/calculus/test_sympy.py" sage -t -long "devel/sage/sage/calculus/wester.py" sage -t -long "devel/sage/sage/calculus/functions.py" sage -t -long "devel/sage/sage/calculus/tests.py" sage -t -long "devel/sage/sage/calculus/functional.py" sage -t -long "devel/sage/sage/plot/line.py" sage -t -long "devel/sage/sage/plot/plot3d/transform.pyx" sage -t -long "devel/sage/sage/interfaces/lisp.py" sage -t -long "devel/sage/sage/interfaces/expect.py" sage -t -long "devel/sage/sage/interfaces/tests.py" sage -t -long "devel/sage/sage/interfaces/maxima.py" sage -t -long "devel/sage/sage/schemes/elliptic_curves/ell_generic.py" sage -t -long "devel/sage/sage/functions/log.py" sage -t -long "devel/sage/sage/functions/wigner.py" sage -t -long "devel/sage/sage/functions/trig.py" sage -t -long "devel/sage/sage/functions/piecewise.py" sage -t -long "devel/sage/sage/functions/orthogonal_polys.py" sage -t -long "devel/sage/sage/functions/special.py" sage -t -long "devel/sage/sage/functions/other.py" sage -t -long "devel/sage/sage/symbolic/expression_conversions.py" sage -t -long "devel/sage/sage/symbolic/benchmark.py" sage -t -long "devel/sage/sage/symbolic/relation.py" sage -t -long "devel/sage/sage/symbolic/assumptions.py" sage -t -long "devel/sage/sage/symbolic/constants.py" sage -t -long "devel/sage/sage/symbolic/power_helper.pyx" sage -t -long "devel/sage/sage/symbolic/expression.pyx" sage -t -long "devel/sage/sage/symbolic/ring.pyx" sage -t -long "devel/sage/sage/symbolic/pynac.pyx" Total time for all tests: 6074.9 seconds [1] http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha1-sage.math.washington.edu-x86_64-Linux.tar.gz -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: "Sage:" in doctests
On Sep 21, 2009, at 9:35 PM, Minh Nguyen wrote: > > Hi Robert, > > On Tue, Sep 22, 2009 at 2:28 PM, Robert Bradshaw > wrote: > > > >> How about a sage -lint to detect things like this? > > Something like that has been put forward as an enhancement to the > merge script. The idea is documented at the Sage release management > wiki page [1]. The merge script has enough options as it is, and it would be nice to be able to run it on a set of files before submitting a patch as well. The merge script could call it. - Robert --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: "Sage:" in doctests
Hi Robert, On Tue, Sep 22, 2009 at 2:28 PM, Robert Bradshaw wrote: > How about a sage -lint to detect things like this? Something like that has been put forward as an enhancement to the merge script. The idea is documented at the Sage release management wiki page [1]. [1] http://wiki.sagemath.org/release -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: uninstall spkg
On Sep 21, 2009, at 4:38 PM, William Stein wrote: > > On Mon, Sep 21, 2009 at 3:48 PM, Ralf Hemmecke > wrote: >> >> Hello, >> >> just for testing purposes, I'd need to uninstall an spkg. >> Can that be done via a sage call with some specific option? >> >> I need the inverse of '-i packagename'. >> >> If this is non-automatized, how can I undo an installation by hand? >> >> Is it enough to remove the respective file under spkg/installed, >> so that >> sage does no longer recognize that the package is actually still >> installed? > > Yes, that will work perfectly. Of course, you will still be able to use any installed data/libraries. - Robert --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: "Sage:" in doctests
On Sep 21, 2009, at 3:53 PM, Jason Grout wrote:
> John H Palmieri wrote:
>> Ticket #6439 suggests that if code has
>>
>>Sage: ...
>>
>> in an EXAMPLES block, then it should be flagged as an error, because
>> presumably the author intended it to say
>>
>>sage: ...
>>
>> and with "Sage: ..." the example isn't actually doctested. I vote
>> against this change: I don't see a reason why we should try to detect
>> this typo more than anything else. (Or if we want to make this
>> change, should we also flag "sgae:", for instance?) Note that with
>> "sage -t -verbose ..." you can see exactly which tests are being run.
>> Referees should also be on the lookout for any typos, including ones
>> like this. So I would like the ticket to be closed without fixing it,
>> but I think this deserves some discussion.
>>
>> Votes for closing without fixing?
>>
>
> Or we might do something like:
>
> if the lowercased characters before a single colon comprise between 3
> and 4 of the letters in "sage", and it's not "sage: ", then flag a
> possible error.
>
> Or something like a regexp like the following:
>
> ^[ ]*[SAGEsage]{3,5}:
>
> I'm all for making people's jobs easier by automating things and
> catching typos, even if we don't catch everything.
How about a sage -lint to detect things like this?
- Robert
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.2.alpha2 doctest failures on OS X 10.5.8
Hi folks, Compiling from source went OK on 64-bit bsd.math (OS X 10.5.8). But I first replaced Fortran, cliquer and ECL with * Fortran at http://sage.math.washington.edu/home/mvngu/apps/fortran-OSX64-20090120.spkg * cliquer at #6681, http://trac.sagemath.org/sage_trac/ticket/6681 * ECL at #6883, http://trac.sagemath.org/sage_trac/ticket/6883 Here is the only doctest failure on 64-bit OS X 10.5.8: sage -t -long "-4.1.2.alpha2/devel/sage/sage/interfaces/maxima.py" ** File "/Volumes/LACIE/scratch/mvngu/sandbox-64/sage-4.1.2.alpha2/devel/sage/sage/interfaces/maxima.py", line 2108: sage: list(v) Expected: [0, x, 2*x^2, 3*x^3, 4*x^4, 5*x^5] Got: [0, x, , 3*x^3, 4*x^4, 5*x^5] ** 1 items had failures: 1 of 4 in __main__.example_64 ***Test Failed*** 1 failures. For whitespace errors, see the file /scratch/mvngu/sandbox-64/sage-4.1.2.alpha2/tmp/.doctest_maxima.py [17.3 s] This is a known failure and can be fixed by the patch at ticket #6883. -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Sage 4.1.2.alpha2 doctest failures on OS X 10.5.8
Hi folks, Compiling Sage 4.1.2.alpha2 went OK on 32-bit bsd.math (OS X 10.5.8). Here are the doctest failures for 32-bit mode: ** doctest failures on 32-bit OS X 10.5.8 ** sage -t -long "-4.1.2.alpha2/devel/sage/sage/crypto/boolean_function.pyx" ** File "/Volumes/LACIE/scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/devel/sage/sage/crypto/boolean_function.pyx", line 1013: sage: B.nonlinearity() Expected: 222 Got: 217 ** 1 items had failures: 1 of 6 in __main__.example_36 ***Test Failed*** 1 failures. For whitespace errors, see the file /scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/tmp/.doctest_boolean_function.py [5.4 s] sage -t -long "-4.1.2.alpha2/devel/sage/sage/interfaces/expect.py" ** File "/Volumes/LACIE/scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/devel/sage/sage/interfaces/expect.py", line 1599: sage: gp(10.^80)._sage_repr() Expected nothing Got: '1.000e80' ** 1 items had failures: 1 of 3 in __main__.example_45 ***Test Failed*** 1 failures. For whitespace errors, see the file /scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/tmp/.doctest_expect.py [14.6 s] sage -t -long "-4.1.2.alpha2/devel/sage/sage/interfaces/gp.py" ** File "/Volumes/LACIE/scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/devel/sage/sage/interfaces/gp.py", line 567: sage: repr(gp(10.^80)).replace(gp._exponent_symbol(), 'e') Expected nothing Got: '1.000e80' ** 1 items had failures: 1 of 4 in __main__.example_26 ***Test Failed*** 1 failures. For whitespace errors, see the file /scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/tmp/.doctest_gp.py [4.2 s] sage -t -long "-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx" ** File "/Volumes/LACIE/scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx", line 3940: sage: x.stable_hash() Expected: 173100285919 Got: -845955105 ** File "/Volumes/LACIE/scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx", line 4849: sage: s.stable_hash() Expected: 173100285919 Got: -845955105 ** File "/Volumes/LACIE/scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx", line 1976: sage: m.stable_hash() Expected: 173100285919 Got: -845955105 ** 3 items had failures: 1 of 4 in __main__.example_128 1 of 5 in __main__.example_165 1 of 5 in __main__.example_48 ***Test Failed*** 3 failures. For whitespace errors, see the file /scratch/mvngu/sandbox-32/sage-4.1.2.alpha2/tmp/.doctest_pbori.py [6.1 s] -- The following tests failed: sage -t -long "-4.1.2.alpha2/devel/sage/sage/crypto/boolean_function.pyx" sage -t -long "-4.1.2.alpha2/devel/sage/sage/interfaces/expect.py" sage -t -long "-4.1.2.alpha2/devel/sage/sage/interfaces/gp.py" sage -t -long "-4.1.2.alpha2/devel/sage/sage/rings/polynomial/pbori.pyx" -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.2.alpha2 released
On Tue, 22 Sep 2009 at 11:15AM +1000, Minh Nguyen wrote: > Please test and report all problems. On Ubuntu Jaunty amd64, building ecl failed with $MAKE='make -j3': if test -f ../CROSS-DPP ; then ../CROSS-DPP /var/tmp/sage-4.1.2.alpha2/spkg/build/ecl-9.8.4/src/src/c/symbol.d symbol.c ; else ./dpp /var/tmp/sage-4.1.2.alpha2/spkg/build/ecl-9.8.4/src/src/c/symbol.d symbol.c ; fi /bin/sh: ./dpp: not found /bin/sh: ./dpp: not found make[4]: *** [main.c] Error 127 make[4]: *** Waiting for unfinished jobs make[4]: *** [symbol.c] Error 127 make[4]: Leaving directory `/var/tmp/sage-4.1.2.alpha2/spkg/build/ecl-9.8.4/src/build/c' make[3]: *** [libeclmin.a] Error 2 make[3]: Leaving directory `/var/tmp/sage-4.1.2.alpha2/spkg/build/ecl-9.8.4/src/build' make[2]: *** [all] Error 2 make[2]: Leaving directory `/var/tmp/sage-4.1.2.alpha2/spkg/build/ecl-9.8.4/src' Failed to build ECL ... exiting This sort of thing was mentioned in ticket #6883 and on this list [1]. With $MAKE=make, it built. Dan 1. http://groups.google.com/group/sage-devel/browse_thread/thread/6b7a4dc5fd5e0ef8/da984bc7e72758b7?#da984bc7e72758b7 -- --- Dan Drake - http://mathsci.kaist.ac.kr/~drake --- signature.asc Description: Digital signature
[sage-devel] Fwd: [sage-release] Re: Sage 4.1.2.alpha2 released
-- Forwarded message -- From: Minh Nguyen Date: Tue, Sep 22, 2009 at 1:22 PM Subject: Re: [sage-release] Re: Sage 4.1.2.alpha2 released To: sage-rele...@googlegroups.com Hi William, On Tue, Sep 22, 2009 at 12:13 PM, William Stein wrote: > I finally fixed this. See > > http://trac.sagemath.org/sage_trac/ticket/6981 > > Somebody needs to referee that. It's an updated of the standard > fortran spkg so that it seamlessly works on OS X 64-bit. I can test these updated packages on OS X 10.5 (bsd.math) and OS X 10.4 (I now have access to that platform). But I have to leave the testing on OS X 10.6 to someone else who has access to Snow Leopard, since I don't have access to a machine running 10.6. -- Regards Minh Van Nguyen -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.2.alpha2 released
On Tue, Sep 22, 2009 at 11:15 AM, Minh Nguyen wrote: > Please test and report all problems. Building Sage 4.1.2.alpha2 from source on sage.math went OK. All doctests pass. This is a bit surprising because I had some doctest failures while merging tickets for that release. -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Bug(?) in the FLINT version that SAGE uses
Dear all, Yesterday I ran into a problem when using the FLINT pseudo division methods in SAGE. Below I am copying part of an email I sent to Bill Hart already. Sebastian [Bug report] While working on re-implementing QQ[] in SAGE, I came across the following inconsistency. From the FLINT 1.4.0 manual, I think the methods fmpz_poly_pseudo_divrem and fmpz_poly_pseudo_div should return the same quotient. But using the "div" method I get A = x^4-4*x^2+2*x+2 B = x-2560 Q = x^3+2560*x^2+6553596*x+3892303874 m = 0 whereas the "divrem" yields A = x^4-4*x^2+2*x+2 B = x-2560 Q = x^3+2560*x^2+6553596*x+16777205762 m = 0 The second answer is the correct one. Temporarily, I have now changed the relevant Cython code to cdef fmpz_poly_t rem fmpz_poly_init(rem) fmpz_poly_pseudo_divrem(q.num, rem, &m, a.num, b.num) fmpz_poly_clear(rem) # fmpz_poly_pseudo_div(q.num, &m, a.num, b.num) and it seems to work fine, as far as many random comparisons between the output of "f // g" with new QQ[] and with the old QQ[] suggest. Here is another example, for which the output doesn't agree: f = -10*x^6 + x^5 + 2*x^4 - x^3 + 2*x^2 - x - 1 g = 75*x^4 - 1/2*x^3 - x^2 + 37/3*x - 1/124 In case this helps, I am working with SAGE 4.1.2.alpha0 under Ubuntu 8.10. --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 4.1.2.alpha2 released
On Sep 21, 6:15 pm, Minh Nguyen wrote: > Please test and report all problems. On sage.math, using the prebuilt binary, I'm getting a ton of errors, mostly of the sort TypeError: Unable to start maxima John --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Another free maths software directory
Check out this: http://cadadr.org/fm/ - Hazem --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Sage 4.1.2.alpha2 released
Hi folks, This release has been slated to be out the door before Review Day 1 to be held on 22nd September 2009. Anyone who would like to participate during Review Day 1, please put your name down at the wiki page http://wiki.sagemath.org/review1 and what you would like to work on. Ideally, your work during Review Day 1 should use Sage 4.1.2.alpha2 as base. The source and binary tarballs are available at http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha2.tar http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha2-sage.math.washington.edu-x86_64-Linux.tar.gz and the upgrade path is http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha2/ Please test and report all problems. In this release, we have some updated packages, but not enough to ensure that Sage builds seamlessly on 64-bit mode OS X 10.5. If you're upgrading on 64-bit OS X 10.5, you might experience problems building cliquer and ECL. Apart from the custom-built Fortran compiler at http://sage.math.washington.edu/home/mvngu/apps/fortran-OSX64-20090120.spkg you should use the updated cliquer package at ticket #6681 and the ECL package at #6883. Remember to issue the command export SAGE64=yes Upgrading or building on 64-bit openSUSE 11.1 can result in a compile error as the cliquer spkg shipped with Sage 4.1.2.alpha2 is known to fail to compile on various 64-bit platforms. The known 64-bit platforms include 64-bit mode OS X 10.5, 64-bit openSUSE 11.1, and 64-bit Fedora 11. If you're building or upgrading on any of those platforms, you should use the cliquer package at #6681. The following tickets were merged in Sage 4.1.2.alpha2: #3133: Jason Grout: allow parametric_plot and parametric_plot3d to take a vector as input [Reviewed by Karl-Dieter Crisman] #3835: John Cremona: Make an algebraic closure function [Reviewed by Mike Hansen] #4786: Karl-Dieter Crisman, Burcin Erocal: fix some bugs / typos in the solve function [Reviewed by Burcin Erocal, Karl-Dieter Crisman] #4948: Felix Lawrence: implement the transfer of Mathematica lists back to Sage [Reviewed by William Stein, Minh Van Nguyen] #5145: Karl-Dieter Crisman: increase default plot_points value for contour_plot [Reviewed by Jason Grout] #5347: John Cremona: divides() may fail for 1 on the rhs. [Reviewed by Mike Hansen] #5758: John Palmieri: weird "hello" bug in homset coerce! [Reviewed by Mike Hansen] #5858: Jonathan J. Hunt: use sage-native-execute to start octave [Reviewed by Jason Grout] #5900: Tim Abbott: Add support for system python != Sage python [Reviewed by Mike Hansen] #6177: Michael Brickenstein, Alexander Dreyer, Martin Albrecht: Update PolyBoRi to newest upstream release [Reviewed by David Kirkby, Alex Ghitza, Burcin Erocal] #6197: Karl-Dieter Crisman: conversion of binomial fails [Reviewed by Mike Hansen] #6325: David Joyner: optional doctest failure -- linear algebra constructions.rst [Reviewed by Mike Hansen] #6328: David Joyner: optional doctest failure -- bugs in the graph theory section of constructions guide [Reviewed by Mike Hansen] #6343: Nicolas M. Thiéry: Adds TestSuite(object).run() generic testing framework [Reviewed by Mike Hansen, Minh Van Nguyen] #6441: Sebastian Pancratz: Charpoly (plus adjoint and det) [Reviewed by Rob Beezer, Yann Laigle-Chapuy] #6521: Karl-Dieter Crisman, Jason Grout: replace .copy() with .__copy__() in matrix/matrix0.pyx [Reviewed by Jason Grout, Karl-Dieter Crisman, Minh Van Nguyen] #6545: Martin Albrecht: sorting of ideal bases [Reviewed by John Perry] #6597: Nicolas M. Thiéry: SetMorphism: 100% doctest + equality + pickling; depends on #6343 [Reviewed by Mike Hansen] #6609: David Kirkby: GNUism in lcalc-20080205.p2 passing GNU flags directly to the Sun assembler. [Reviewed by Minh Van Nguyen] #6634: Marshall Hampton: biopython 1.49b broken with python-2.6; biopython upgrade [Reviewed by Alex Ghitza] #6636: Karl-Dieter Crisman: Simplification of factorials and binomial coefficients is not very good [Reviewed by Mike Hansen] #6652: Ralf Hemmecke: should not have algebra structure on streams [Reviewed by Florent Hivert] #6663: Marshall Hampton: add new 4ti2 experimental package [Reviewed by David Joyner, Alex Ghitza, Bjarke Hammersholt Roune, Mike Hansen, David Perkinson] #6749: Nathann Cohen: Knapsack algorithm [Reviewed by David Joyner] #6750: Simon King, David J. Green: New version of optional Group Cohomology spkg [Reviewed by John Palmieri, David Joyner, Mikael Vejdemo Johansson] #6759: David Kirkby: Update sqlite to latest release - needed for Sun's compiler [Reviewed by Minh Van Nguyen] #6774: Nathann Cohen: tour Graph Theory [Reviewed by Jason Grout] #6806: Minh Van Nguyen: typo in patch of ticket #6396: primes_of_degree_one is broken for relative extensions [Reviewed by Karl-Dieter Crisman] #6827: Carlo Hamalainen: probability distributions doctests + general discrete distribution [Reviewed by Mike Hansen] #6848: John Palmieri: "Definition:" messed up in
[sage-devel] Re: "Sage:" in doctests
On Mon, Sep 21, 2009 at 4:54 PM, Minh Nguyen wrote: > > On Tue, Sep 22, 2009 at 8:24 AM, John H Palmieri > wrote: >> >> Ticket #6439 suggests that if code has >> >> Sage: ... >> >> in an EXAMPLES block, then it should be flagged as an error, because >> presumably the author intended it to say >> >> sage: ... >> >> and with "Sage: ..." the example isn't actually doctested. > > When writing doctests, do people actually type in "sage:", "Sage:", > "SAGE:" or other variations rather than copying it from the Sage > command line? I would usually load the command line, type in the > doctesting code, and copy the input and output into the relevant > docstring. This is a simple use case, but any typo input at the > command line would result in Sage complaining. I find that a good way > to catch typos early before submiting patches. > I use the notebook to make a little session, then click on "Text" in the upper right, which in most cases formats the output to make it suitable for doctesting. -- William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: "Sage:" in doctests
On Tue, Sep 22, 2009 at 8:24 AM, John H Palmieri wrote: > > Ticket #6439 suggests that if code has > > Sage: ... > > in an EXAMPLES block, then it should be flagged as an error, because > presumably the author intended it to say > > sage: ... > > and with "Sage: ..." the example isn't actually doctested. When writing doctests, do people actually type in "sage:", "Sage:", "SAGE:" or other variations rather than copying it from the Sage command line? I would usually load the command line, type in the doctesting code, and copy the input and output into the relevant docstring. This is a simple use case, but any typo input at the command line would result in Sage complaining. I find that a good way to catch typos early before submiting patches. My 2-cent. -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: uninstall spkg
On Mon, Sep 21, 2009 at 3:48 PM, Ralf Hemmecke wrote: > > Hello, > > just for testing purposes, I'd need to uninstall an spkg. > Can that be done via a sage call with some specific option? > > I need the inverse of '-i packagename'. > > If this is non-automatized, how can I undo an installation by hand? > > Is it enough to remove the respective file under spkg/installed, so that > sage does no longer recognize that the package is actually still installed? Yes, that will work perfectly. > I actually don't care whether the files that my package installed via > "make install" are still there, I only want that 'sage -i pkgname' > installs the package again (no, I don't want to give the -f option). You can also do "sage -f pkgname" to force install of the package even if it has already been installed. > > Ralf > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: "Sage:" in doctests
On Sep 21, 3:53 pm, Jason Grout wrote:
>
> Or we might do something like:
>
> if the lowercased characters before a single colon comprise between 3
> and 4 of the letters in "sage", and it's not "sage: ", then flag a
> possible error.
>
> Or something like a regexp like the following:
>
> ^[ ]*[SAGEsage]{3,5}:
>
> I'm all for making people's jobs easier by automating things and
> catching typos, even if we don't catch everything.
But I don't think we should try to be too clever. For instance, what
if someone *wants* "SGA:" in a docstring? Can we envision a situation
where someone would want to use "Sage:"? We might end up shooting
ourselves in the foot if we try to catch too many possible "typos".
John
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: "Sage:" in doctests
John H Palmieri wrote:
> Ticket #6439 suggests that if code has
>
>Sage: ...
>
> in an EXAMPLES block, then it should be flagged as an error, because
> presumably the author intended it to say
>
>sage: ...
>
> and with "Sage: ..." the example isn't actually doctested. I vote
> against this change: I don't see a reason why we should try to detect
> this typo more than anything else. (Or if we want to make this
> change, should we also flag "sgae:", for instance?) Note that with
> "sage -t -verbose ..." you can see exactly which tests are being run.
> Referees should also be on the lookout for any typos, including ones
> like this. So I would like the ticket to be closed without fixing it,
> but I think this deserves some discussion.
>
> Votes for closing without fixing?
>
Or we might do something like:
if the lowercased characters before a single colon comprise between 3
and 4 of the letters in "sage", and it's not "sage: ", then flag a
possible error.
Or something like a regexp like the following:
^[ ]*[SAGEsage]{3,5}:
I'm all for making people's jobs easier by automating things and
catching typos, even if we don't catch everything.
Jason
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: uninstall spkg
On Sep 21, 2009, at 6:48 PM, Ralf Hemmecke wrote: Hello, just for testing purposes, I'd need to uninstall an spkg. Can that be done via a sage call with some specific option? I need the inverse of '-i packagename'. If this is non-automatized, how can I undo an installation by hand? As far as I know, right now, it isn't possible in an automated fashion. It's something I've wanted as well. I suspect the best way to do this is watch what's installed and then delete those. One way I can think is maintain a list of files installed (e.g., via ls) and then compare the two lists. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo http://www.linkedin.com/in/timlahey smime.p7s Description: S/MIME cryptographic signature
[sage-devel] uninstall spkg
Hello, just for testing purposes, I'd need to uninstall an spkg. Can that be done via a sage call with some specific option? I need the inverse of '-i packagename'. If this is non-automatized, how can I undo an installation by hand? Is it enough to remove the respective file under spkg/installed, so that sage does no longer recognize that the package is actually still installed? I actually don't care whether the files that my package installed via "make install" are still there, I only want that 'sage -i pkgname' installs the package again (no, I don't want to give the -f option). Ralf --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Suspiciously sorted sets
Hi Nick, On 22 Sep., 00:02, Nick Alexander wrote: > Just for the record, "sorted sets" make very little sense. Sure. When I said "unless something implements a __cmp__ method..." I did not mean that one *should* implement it; I just wanted to explain "sorted(...) relies on a __cmp__ method, so if in some context one wants sorted to work then __cmp__ must be implemented". In the case of sets, I totally agree that the user should transform the set into a list and then proceed with that, if s/he wants some orderable object. Best regards Simon --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] "Sage:" in doctests
Ticket #6439 suggests that if code has Sage: ... in an EXAMPLES block, then it should be flagged as an error, because presumably the author intended it to say sage: ... and with "Sage: ..." the example isn't actually doctested. I vote against this change: I don't see a reason why we should try to detect this typo more than anything else. (Or if we want to make this change, should we also flag "sgae:", for instance?) Note that with "sage -t -verbose ..." you can see exactly which tests are being run. Referees should also be on the lookout for any typos, including ones like this. So I would like the ticket to be closed without fixing it, but I think this deserves some discussion. Votes for closing without fixing? I say +1. John --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Suspiciously sorted sets
> I'll likely add to Trac a ticket about the need for a comparison > method on sets later today when I get a chance. Just for the record, "sorted sets" make very little sense. It is important to be able to have a set containing anything that is hashable (in the python sense) but not necessarily sortable (again in the python sense). If you can't sort the elements, how can you order the sets themselves? Nick --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Documentation is pretty hard to read...
Nathann Cohen wrote: > I had a question to ask about the documentation we produce for Sage from the A dynamic, lazy-loading, live documentation browser and/or object inspector could be useful. Which layouts are appropriate? Can we use existing libraries? Trees http://api.jquery.com/ http://www.jstree.com/ Miller columns http://en.wikipedia.org/wiki/Miller_Columns http://www.smartclient.com/smartgwt/showcase/#featured_miller_columns I'm sure there are others. The last is actually a Google Web Toolkit (GWT) extension written in Java. Can anyone point out a similar JavaScript widget? Individual topics could float freely or occupy tab widget, say, or even browser tabs. We could save bookmarks and configurations on the server. Unless I'm mistaken, the notebook's introspection system already provides much of what we need to set this up. We "just" need to create an altogether differently organized "worksheet." --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Review Day next Tuesday (22 Sep)
On Sep 21, 2009, at 12:40 PM, Nicolas M. Thiery wrote: > > On Tue, Sep 15, 2009 at 03:46:50PM -0500, Jason Grout wrote: >> >> We have been extremely blessed lately with a load of great >> contributions. Currently, there are: >> >> * 96 tickets that have patches/spkgs and are waiting for review: >> http://trac.sagemath.org/sage_trac/report/10. These tickets have >> been >> waiting for review for up to 10 months! [1] >> >> * 6 tickets that apparently just need a rebase: >> http://trac.sagemath.org/sage_trac/report/19 >> >> William has asked me to announce a Review Day next Tuesday, 22 >> September. The goal is take care of every ticket that has "needs >> review" status and either declare it positive review or give specific >> feedback and put it in the needs work queue. >> >> The wiki page for the review day is: http://wiki.sagemath.org/review1 >> >> If we finish early, then there are a total of 288 tickets with >> patches >> in various states of readiness: http://trac.sagemath.org/sage_trac/ >> report/13 >> >> Minh has been doing a tremendously wonderful job of getting positive >> reviews merged promptly. Let's see how many positive reviews he can >> handle :). > > Please, please, please, finish up to review the remaining > categories on > http://sagetrac.org/sage_trac/wiki/CategoriesCategoriesReview! > > I'll try to join, but Greenwich time won't be very compatible ... Depends on how late you like to stay up :). I won't be able to spend all day on it, but will try to put in a couple of hours. - Robert --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Review Day next Tuesday (22 Sep)
On Tue, Sep 15, 2009 at 03:46:50PM -0500, Jason Grout wrote: > > We have been extremely blessed lately with a load of great > contributions. Currently, there are: > > * 96 tickets that have patches/spkgs and are waiting for review: > http://trac.sagemath.org/sage_trac/report/10. These tickets have been > waiting for review for up to 10 months! [1] > > * 6 tickets that apparently just need a rebase: > http://trac.sagemath.org/sage_trac/report/19 > > William has asked me to announce a Review Day next Tuesday, 22 > September. The goal is take care of every ticket that has "needs > review" status and either declare it positive review or give specific > feedback and put it in the needs work queue. > > The wiki page for the review day is: http://wiki.sagemath.org/review1 > > If we finish early, then there are a total of 288 tickets with patches > in various states of readiness: http://trac.sagemath.org/sage_trac/report/13 > > Minh has been doing a tremendously wonderful job of getting positive > reviews merged promptly. Let's see how many positive reviews he can > handle :). Please, please, please, finish up to review the remaining categories on http://sagetrac.org/sage_trac/wiki/CategoriesCategoriesReview! I'll try to join, but Greenwich time won't be very compatible ... Cheers, Nicolas -- Nicolas M. Thiéry "Isil" http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] update on femhub windows port
Hi, I passed my PhD comps! so I started to work on the femhub windows port (cygwin) and it's *almost* there. Lots of packages need to be fixed, we worked on that with William and Dan Drake yesterday, so gpg et. al numpy matplotlib are all fixed and reported. Then all packages that are also in Sage build in cygwin. After that, VTK has to be fixed, but then it seems to build, only it takes insanely long (an hour or more), so I think I'll skip it for now and enable it later (so mayavi has to be skipped as well). osmesa builds, other packages build, so what remains is hermes2d, which fails too, but I'll fix it. Apart from that, everything else seems to build just fine. I think we are very close to actually provide a windows binary of femhub in the next release, I feel it. So I'll be working on this, and finish it this week. Ondrej --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] HTML5 article from MAA
FYI, for those who have been discussing this: http://mathdl.maa.org/mathDL/55/?pa=content&sa=viewDocument&nodeId=3340 - kcrisman --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Starting R in Sage Chroot
On Mon, Sep 21, 2009 at 8:30 AM, Kay Wanous wrote: > > I think we are going to end up just installing on a completely different > system. The closest I got was to > > export LC_ALL=en_US > > which allowed me to call r.version and not have it error out, but > running it from the program now produces > > > > Unless anyone has any ideas, I think I'm going to give up on this. > > Thanks, > Kay It couldn't hurt for you to try the newest version of R: http://sage.math.washington.edu/home/wstein/patches/r-2.9.2.spkg William --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: factoring zero
On Mon, Sep 21, 2009 at 6:12 AM, kcrisman wrote: > > Somewhat relevant, though not necessarily something we want to > implement in Sage, is Conway's (and others') suggestion that -1 should > be prime. See among others this thread at the mathforum, which at > times would put sage-flame to shame :) though apparently all in good > fun (?) and includes this neat restatement: "The multiplicative group > of the non-zero rationals is the direct product of the cyclic > subgroups generated by "my" primes, namely -1,2,3,5,... ." > > - kcrisman -1 to -1 being prime. :-) --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage in the news
Bill Hart wrote: > An interesting talk by Terry (which I did not attend). > > It would be interesting to see Terry give a talk on the dangers of the > internet for mathematicians. Here are a few: > > * Poor eye health. Constant use of laptop and computer displays leads > to dry eyes which can cause shrivelling of the cornea and eventually > infection, even cutting the length of your life, especially for those > of us who wear contact lenses. /me quickly glances out the window to rest my eyes... > > * Poor posture. Slouching at a computer can cause issues such as > hunched shoulders, lower back pain. /me subconsciously sits up in my straight-back chair > > * Poor health. The lack of physical exercise associated with constant > computer use can lead to poor circulation, increased cholesterol and > increased risk of stroke and cardiac arrest, resulting in early death. > Also, lack of exposure to sunshine leads to chronic shortage of > vitamin D which results in significantly increased risk of cancers and > other serious diseases. /me remembers William and others taking a day or two off to go snowboarding... > > * Culture of instant gratification. The increase in availability of > things *now* means people become impatient and do not want to wait for > any result which cannot be achieved *now*. yep---I see this more increasingly with students too... > > * The impersonality of the textual medium. Communicating exact > intentions through text is difficult. This can result in people > disagreeing and becoming polarised over issues they would otherwise > find common ground on. Furthermore, some people find it much easier to > be rude in text, or on an online forum than in person. /me is very, very grateful for several Sage days that put names and personalities with online nicks. I hope I'm not rude in this reply! > > * Lower reproductive success. The complete failure of hackers to get > girlfriends is well documented. The associated risks to longevity > through lack of companionship are well documented. Well, gee, I'm married and have a nice family :). I hope people don't give up that wonderful experience for bits on a pipe. In fact, it seems that Craig at one time was thinking about something like a Sage Babies group, since several of us (i.e., our spouses) were having babies around the same time... > > * Excessive use of email. Many researchers answer in excess of 300 > emails a week, something which accounts for a significant proportion > of their time. /me wonders if I should really reply to this email... > > In short, if you want a long happy life. Don't use the internet. ahem---don't be *addicted* to the internet :). > > Be well, citizen. I wish you a happy happy joy joy day. Great. Thanks. I wish I could have the five minutes I took reading this message to go outside and do that! :). Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage in the news
Doh, this was supposed to get posted in the thread on Terry Tao's talk. Another problem with the internet. Unintended consequences. Bill. On 21 Sep, 17:14, Bill Hart wrote: > An interesting talk by Terry (which I did not attend). > > It would be interesting to see Terry give a talk on the dangers of the > internet for mathematicians. Here are a few: > > * Poor eye health. Constant use of laptop and computer displays leads > to dry eyes which can cause shrivelling of the cornea and eventually > infection, even cutting the length of your life, especially for those > of us who wear contact lenses. > > * Poor posture. Slouching at a computer can cause issues such as > hunched shoulders, lower back pain. > > * Poor health. The lack of physical exercise associated with constant > computer use can lead to poor circulation, increased cholesterol and > increased risk of stroke and cardiac arrest, resulting in early death. > Also, lack of exposure to sunshine leads to chronic shortage of > vitamin D which results in significantly increased risk of cancers and > other serious diseases. > > * Culture of instant gratification. The increase in availability of > things *now* means people become impatient and do not want to wait for > any result which cannot be achieved *now*. > > * The impersonality of the textual medium. Communicating exact > intentions through text is difficult. This can result in people > disagreeing and becoming polarised over issues they would otherwise > find common ground on. Furthermore, some people find it much easier to > be rude in text, or on an online forum than in person. > > * Lower reproductive success. The complete failure of hackers to get > girlfriends is well documented. The associated risks to longevity > through lack of companionship are well documented. > > * Excessive use of email. Many researchers answer in excess of 300 > emails a week, something which accounts for a significant proportion > of their time. > > In short, if you want a long happy life. Don't use the internet. > > Be well, citizen. I wish you a happy happy joy joy day. > > Bill. > > On 21 Sep, 03:42, Minh Nguyen wrote: > > > > > Hi folks, > > > Here's a news item at iTWire that mentions Sage: > > >http://www.itwire.com/content/view/27887/1090/1/0/ > > > In particular, read on page 2 of that news article. > > > -- > > Regards > > Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage in the news
An interesting talk by Terry (which I did not attend). It would be interesting to see Terry give a talk on the dangers of the internet for mathematicians. Here are a few: * Poor eye health. Constant use of laptop and computer displays leads to dry eyes which can cause shrivelling of the cornea and eventually infection, even cutting the length of your life, especially for those of us who wear contact lenses. * Poor posture. Slouching at a computer can cause issues such as hunched shoulders, lower back pain. * Poor health. The lack of physical exercise associated with constant computer use can lead to poor circulation, increased cholesterol and increased risk of stroke and cardiac arrest, resulting in early death. Also, lack of exposure to sunshine leads to chronic shortage of vitamin D which results in significantly increased risk of cancers and other serious diseases. * Culture of instant gratification. The increase in availability of things *now* means people become impatient and do not want to wait for any result which cannot be achieved *now*. * The impersonality of the textual medium. Communicating exact intentions through text is difficult. This can result in people disagreeing and becoming polarised over issues they would otherwise find common ground on. Furthermore, some people find it much easier to be rude in text, or on an online forum than in person. * Lower reproductive success. The complete failure of hackers to get girlfriends is well documented. The associated risks to longevity through lack of companionship are well documented. * Excessive use of email. Many researchers answer in excess of 300 emails a week, something which accounts for a significant proportion of their time. In short, if you want a long happy life. Don't use the internet. Be well, citizen. I wish you a happy happy joy joy day. Bill. On 21 Sep, 03:42, Minh Nguyen wrote: > Hi folks, > > Here's a news item at iTWire that mentions Sage: > > http://www.itwire.com/content/view/27887/1090/1/0/ > > In particular, read on page 2 of that news article. > > -- > Regards > Minh Van Nguyen --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Group of units in Z_n
On Sep 21, 11:50 am, Rob Beezer wrote: > Hi Karl-Dieter, > > Well, I guess I *am* doing this as I put together something very quick > and sloppy last night, which has helped formulate my ideas for a > better version (this approach was due to some good advice from > William). Let me know if you need something messy and incomplete, but > serviceable, right away. ;-) Good chance I might call on you for > some number-theoretic advice along the way. Nope, not teaching it (or anything at all, in fact) this semester; next up spring 2011. But I think this will help a lot of other people, since Sage is so natural for NT and plus William's book is already out there... - kcrisman > > Rob > > On Sep 21, 6:17 am, kcrisman wrote: > > > > > Rob, > > > Please do this! I am always having to do some hack in my number > > theory class for this, and it is very annoying (as you have > > discovered) not to have this. It is somewhere very far down my to-do > > list for Sage. Actually, I'm surprised there isn't some hidden > > structure where it lurks, as you suggest in your last paragraph. > > Thanks! > > > - kcrisman --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Group of units in Z_n
Hi Karl-Dieter, Well, I guess I *am* doing this as I put together something very quick and sloppy last night, which has helped formulate my ideas for a better version (this approach was due to some good advice from William). Let me know if you need something messy and incomplete, but serviceable, right away. ;-) Good chance I might call on you for some number-theoretic advice along the way. Rob On Sep 21, 6:17 am, kcrisman wrote: > Rob, > > Please do this! I am always having to do some hack in my number > theory class for this, and it is very annoying (as you have > discovered) not to have this. It is somewhere very far down my to-do > list for Sage. Actually, I'm surprised there isn't some hidden > structure where it lurks, as you suggest in your last paragraph. > Thanks! > > - kcrisman --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Suspiciously sorted sets
Hi Simon, Thanks for the explanation and isolating the problem, plus the workaround for getting a unique result. I did have doctesting in the back of my mind, even though it is not necessary at the moment for the patch in question. I'll likely add to Trac a ticket about the need for a comparison method on sets later today when I get a chance. Rob --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Starting R in Sage Chroot
I think we are going to end up just installing on a completely different system. The closest I got was to export LC_ALL=en_US which allowed me to call r.version and not have it error out, but running it from the program now produces Unless anyone has any ideas, I think I'm going to give up on this. Thanks, Kay Minh Nguyen wrote: > Hi Kay, > > On Fri, Sep 18, 2009 at 2:49 AM, Kay Wanous wrote: > > > >> Any ideas? > > This might not be of any help at all but... If you want to limit the > damage that could be done on your system, you might consider > virtualization tools such as VirtualBox OSE, VMware, etc. instead of > using chroot. I have used Sage running within virtualized Linux guests > using VirtualBox OSE and VMware. So far I'm quite happy with both of > these for testing Sage, and haven't run across the problem you > reported above. > --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] sagenb.org going down
I just noticed that it appeared like sagenb.org was down. This happened last week too. It also appears that an automated script seems to pull it back up, as I just have to wait a minute or two for it to come back. How often does sagenb.org go down? Is it a problem on my end, or does it really go down every couple of days for a few minutes? Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: the Sage notebook
On 20-Sep-09, at 5:34 AM, William Stein wrote: > > Hi, > > If anybody is planning on working on the Sage notebook during the next > week, please > keep in close communication with me and or this list. I'm working on > separating out the > notebook out as a completely separate Python library. If you can make it possible to coherently load libraries of code in the notebook (refer to other worksheets? some global worksheet loaded all the time?) I am almost considering moving to the notebook from Emacs. Nick --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Group of units in Z_n
Rob, Please do this! I am always having to do some hack in my number theory class for this, and it is very annoying (as you have discovered) not to have this. It is somewhere very far down my to-do list for Sage. Actually, I'm surprised there isn't some hidden structure where it lurks, as you suggest in your last paragraph. Thanks! - kcrisman --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: factoring zero
Somewhat relevant, though not necessarily something we want to implement in Sage, is Conway's (and others') suggestion that -1 should be prime. See among others this thread at the mathforum, which at times would put sage-flame to shame :) though apparently all in good fun (?) and includes this neat restatement: "The multiplicative group of the non-zero rationals is the direct product of the cyclic subgroups generated by "my" primes, namely -1,2,3,5,... ." - kcrisman --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: the Sage notebook
William Stein wrote: > Hi, > > If anybody is planning on working on the Sage notebook during the next > week, please > keep in close communication with me and or this list. I'm working on > separating out the > notebook out as a completely separate Python library. You are probably aware, but just in case: there are a few notebook related tickets that are up for review or have been merged into 4.1.2. Jason -- Jason Grout --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Review Day next Tuesday (22 Sep)
William Stein wrote: > On Sun, Sep 20, 2009 at 4:11 PM, Marshall Hampton wrote: >> Cool. Tuesdays aren't very good for me, but I will do my best to do > > It'll only be on Tuesday this time. There are now 4 people up at > > http://wiki.sagemath.org/review1 > > I wish there were more than 4, but that is a good start. > What time should we start? > I plan on starting by 8:30AM Central Time. I realize that might be kind of early for the folks on the west coast, though. If Karl or other East Coast people want to start even earlier, they are more than welcome. Thanks, Jason -- Jason Grout --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Gnuplotpy optional package fails to install.
That's the same error I get, on 32 bit linux. They said it was a regression bug from Python 2.6. See: http://groups.google.com/group/sage-devel/browse_thread/thread/98aba5c1385815ab/c249718279e08ffb?lnk=gst&q=gnuplotpy#c249718279e08ffb --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Suspiciously sorted sets
Hi!
On Sep 21, 10:22 am, Simon King wrote:
[...]
> So, unless someone implements __cmp__ (or similar) methods for
> Set_object_enumerated, you can't expect to get anything meaningful out
> of the sorting.
If your question is just about getting *some* unique result (say, for
a doc test): You can sort the elements of your list first, and then
you have a list of list (rather than a list of sets) that you can sort
in a unique way.
sage: g = Graph()
sage: g.add_vertices(Subsets(3,2))
sage: g.vertices()
[{2, 3}, {1, 2}, {1, 3}]
sage: sorted([sorted(list(V)) for V in g.vertices()])
[[1, 2], [1, 3], [2, 3]]
sage: Subsets(3,2).list()
[{1, 2}, {1, 3}, {2, 3}]
sage: sorted([sorted(list(V)) for V in Subsets(3,2)])
[[1, 2], [1, 3], [2, 3]]
Cheers,
Simon
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Suspiciously sorted sets
Hi Rob!
On Sep 21, 2:15 am, Rob Beezer wrote:
> sage: g = Graph()
> sage: g.add_vertices(Subsets(3,2))
> sage: g.vertices()
> [{2, 3}, {1, 2}, {1, 3}]
> sage: sorted(g.vertices())
> [{1, 3}, {1, 2}, {2, 3}]
> sage: Subsets(3,2).list()
> [{1, 2}, {1, 3}, {2, 3}]
> sage: sorted(Subsets(3,2).list())
> [{2, 3}, {1, 3}, {1, 2}]
I think the problem is that there is no proper ordering defined for
sage.sets.set.Set_object_enumerated:
sage: S = Subsets(3,2).list()[0]
sage: T = Subsets(3,2).list()[1]
sage: S
{1, 2}
sage: T
{1, 3}
sage: type(S)
sage: S < T
True
sage: T < S
True
sage: S==T
False
So, unless someone implements __cmp__ (or similar) methods for
Set_object_enumerated, you can't expect to get anything meaningful out
of the sorting.
Best regards,
Simon
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: ucontext.h
On Mon, Sep 21, 2009 at 12:37 AM, William Stein wrote: > Could you consider changing src/gc/mach_dep.c in ECL so that it > includes sys/ucontext.h instead of ucontext.h. This fixes a build > issue on OS X 10.6, as described here: I will try with this hack. This is a recently solved problem in the Boehm-Weiser garbage collector. I was hoping to add an newer version before releasing ECL, but it is taking them a lot of time to produce a release. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com --~--~-~--~~~---~--~~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~--~~~~--~~--~--~---
