Sage 6.10.beta5 released

[Volker Braun]

As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html

4ca26b3 Updated Sage version to 6.10.beta5

f04c3c7 Trac #19249: Interface with TdLib

23f93e2 Trac #19600: correct a few typoes

5689f93 Trac #19533: Add a method to find a vector x such that Q(x) = C, where Q is a quadratic form and C is a constant.

3a586db Trac #19392: Add tetrahedral poset code

7bf2275 Trac #19593: interval-posets in Tamari lattice should be hashable..

9e84001 Trac #19584: Clean up NTL comparisons

a6c6865 Trac #19508: Implementing RijndaelGF

5911b2f Trac #19276: precision problem computing heights on elliptic curves

9cafbb6 Trac #19471: COIN backend: More basis status and tableau data functions

2ec5601 Trac #19582: Upgrade boot_cropped to 1.58.0

41862d0 Trac #19588: typos in "iterator" spelling

e8a2fe9 Trac #19579: Declare NTL types as cppclass

be20067 Trac #19480: Fix permissions of qepcad.help

14f5b40 Trac #19472: GLPK backend: More basis status and tableau data functions

13f0610 Trac #17481: Python does not need dpkg-dev anymore on multiarch debians

9ae39ee Trac #19432: Small fixes to the developer's walkthrough

d5d7b10 Trac #19575: Conversion PARI t_STR -> Python str should not keep quotes

5d5d0c3 Trac #19574: src/sage_setup/find.py :  find_extra_files break doctests if they are not run from SAGE_ROOT directory

93d275b Trac #19501: Factor() of small integer does not check algorithm-keyword

44fed19 Trac #16637: has_finite_order of EllipticCurvePoint performs useless computations

3414e18 Trac #19559: method -> algorithm, part 2

a24c10d Trac #19566: Jupyter rich output compatibility

8888057 Trac #19561: enforce Sage integers in Krawtchouk

f41a40b Trac #19495: Fixes a bug in is_mutation_finite for ClusterSeed

34ce791 Trac #19400: move documentation of asymptotic expansion to sage.asymptotic

d2fd8ac Trac #19296: Generating function in FindStat interface

fbabbf1 Trac #19113: LatticePoset: Return type category of product()

0d3caa0 Updated Sage version to 6.10.beta4

[Rob Beezer]

Did the source tarball go out to the mirrors?

I'm not seeing it at the two places I use regularly (nor two other places that
are otherwise up-to-date):

http://mirrors.mit.edu/sage/devel/

http://www.cecm.sfu.ca/sage/devel/

Thanks,
Rob

> --
> You received this message because you are subscribed to the Google Groups
> "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email
> to sage-release...@googlegroups.com
> <mailto:sage-release...@googlegroups.com>.
> To post to this group, send email to sage-r...@googlegroups.com
> <mailto:sage-r...@googlegroups.com>.
> Visit this group at http://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

[Harald Schilly]

On Mon, Nov 23, 2015 at 11:44 PM, Rob Beezer <bee...@ups.edu> wrote:
> Did the source tarball go out to the mirrors?

I'm not sure, but this is the master server from which all the others
are feeding from
http://files.sagemath.org/devel/index.html

-- h

[Rob Beezer]

And that page does not list beta5, and the tarball does not seem available from
there.

[Volker Braun]

thanks, fixed.

[Justin C. Walker]

On Nov 22, 2015, at 12:45 , Volker Braun wrote:

> As always, you can get the latest beta version from the "develop" git
> branch. Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html

Built from the tarball on two OS X systems, 10.6.8 (Dual 6-core Xeons) and 10.10.5 (Quad-core Core i7). Builds completed w. no problems.

Testing ('ptestlong'):
10.10.5: all passed
10.6.8: one failure:
sage -t --long --warn-long 108.1 src/sage/homology/simplicial_complex.py # Bad exit: 2

Running this by itself passed.

This prompts a couple of questions (out of curiosity):
- I trimmed the "--long --warn-long 108.1" part, but sage replaced them, albeit with a shorter time (105.2). How do it know? And why the difference?
- Why the "long" flags? The test ran in ~4 seconds.

Thanks!

Justin

--
Justin C. Walker
Curmudgeon-at-large
Director
Institute for the Absorption of Federal Funds
----
186,000 Miles per Second
Not just a good idea:
it's the law!
----

[Volker Braun]

On Tuesday, November 24, 2015 at 9:42:31 PM UTC+1, Justin C. Walker wrote:

This prompts a couple of questions (out of curiosity):
 - I trimmed the "--long --warn-long 108.1" part, but sage replaced them, albeit with a shorter time (105.2).  How do it know?  And why the difference?
 - Why the "long" flags?  The test ran in ~4 seconds.

The warn-long cutoff is scaled based on the speed of your computer as measured by the last successful test run.

Tests should be near-instantaneous. Everything that takes second(s) is --long. You might think a second is nothing, but if you have 1000s of files with 100s of doctests then things tend to add up.

[Rob Beezer]

On SageMathCloud, built from source, passes long tests ("ptestlong").

@Cremona - none of the elliptic curve tests timed-out this time.

Development Images and Build Logs available at:
https://cloud.sagemath.com/projects/53b77207-8614-4086-a032-432af4b4cdbd/files/sage-dev-images/

On 11/22/2015 12:45 PM, Volker Braun wrote:

[Justin C. Walker]

Thanks; makes sense.

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's Income
-----------
Nobody knows the trouble I've been
-----------

[Sébastien Labbé]

With optional sage packages coxeter3 and cryptominisat, I get some optional doctests that are broken:

----------------------------------------------------------------------
sage -t --warn-long 27.7 src/sage/rings/polynomial/multi_polynomial_sequence.py  # 1 doctest failed
sage -t --warn-long 27.7 src/sage/combinat/kazhdan_lusztig.py  # 1 doctest failed
sage -t --warn-long 27.7 src/sage/libs/coxeter3/coxeter_group.py  # 7 doctests failed
sage -t --warn-long 27.7 src/sage/libs/coxeter3/coxeter.pyx  # 25 doctests failed
----------------------------------------------------------------------

The first is:

sage -t --warn-long 27.7 src/sage/rings/polynomial/multi_polynomial_sequence.py
**********************************************************************
File "src/sage/rings/polynomial/multi_polynomial_sequence.py", line 1381, in sage.rings.polynomial.multi_polynomial_sequence.PolynomialSequence_gf2.solve
Failed example:
    sol = S.solve(algorithm='sat'); sol  # optional - cryptominisat
Expected nothing
Got:
    [{y: 1, z: 0, x: 0}]
**********************************************************************

The others are all of the following types:

**********************************************************************
File "src/sage/libs/coxeter3/coxeter_group.py", line 29, in sage.libs.coxeter3.coxeter_group.CoxeterGroup.__classcall__
Failed example:
    CoxeterGroup(['B',2])                                     # optional - coxeter3
Expected:
    Coxeter group of type ['B', 2] implemented by Coxeter3
Got:
    doctest:50: DeprecationWarning: coxeter_matrix() is deprecated. Use CoxeterMatrix() instead
    See http://trac.sagemath.org/17798 for details.
    Warning, differing Coxeter matrices
    Coxeter group of type ['B', 2] implemented by Coxeter3
**********************************************************************
File "src/sage/libs/coxeter3/coxeter_group.py", line 42, in sage.libs.coxeter3.coxeter_group.CoxeterGroup.__init__
Failed example:
    CoxeterGroup(['A',2])                                     # optional - coxeter3
Expected:
    Coxeter group of type ['A', 2] implemented by Coxeter3
Got:
    Warning, differing Coxeter matrices
    Coxeter group of type ['A', 2] implemented by Coxeter3
**********************************************************************
File "src/sage/libs/coxeter3/coxeter_group.py", line 44, in sage.libs.coxeter3.coxeter_group.CoxeterGroup.__init__
Failed example:
    TestSuite(CoxeterGroup(['A',2])).run()                    # optional - coxeter3
Expected nothing
Got:
    doctest:283: DeprecationWarning: coxeter_matrix() is deprecated. Use CoxeterMatrix() instead
    See http://trac.sagemath.org/17798 for details.
    Warning, differing Coxeter matrices
**********************************************************************
File "src/sage/libs/coxeter3/coxeter_group.py", line 57, in sage.libs.coxeter3.coxeter_group.CoxeterGroup._repr_
Failed example:
    W = CoxeterGroup(['A', 3], implementation='coxeter3'); W      # optional - coxeter3 # indirect doctest
Expected:
    Coxeter group of type ['A', 3] implemented by Coxeter3
Got:
    Warning, differing Coxeter matrices
    Coxeter group of type ['A', 3] implemented by Coxeter3
**********************************************************************

Using --optional=benzene,bliss,buckygen,cbc,coxeter3,cryptominisat,database_cremona_ellcurve,database_gap,database_odlyzko_zeta,database_pari,database_stein_watkins,
database_symbolic_data,dot2tex,gambit,gap_packages,gcc,gdb,mcqd,modular_decomposition,mpir,nauty,plantri,python2,sage,scons,tides

I do not get other broken doctests.

Sébastien

[Sébastien Labbé]

On Friday, November 27, 2015 at 3:49:49 PM UTC+1, Sébastien Labbé wrote:

With optional sage packages coxeter3 and cryptominisat, I get some optional doctests that are broken:

----------------------------------------------------------------------
sage -t --warn-long 27.7 src/sage/rings/polynomial/multi_polynomial_sequence.py  # 1 doctest failed

Fix needs review at:
http://trac.sagemath.org/ticket/19652
 

sage -t --warn-long 27.7 src/sage/combinat/kazhdan_lusztig.py  # 1 doctest failed
sage -t --warn-long 27.7 src/sage/libs/coxeter3/coxeter_group.py  # 7 doctests failed
sage -t --warn-long 27.7 src/sage/libs/coxeter3/coxeter.pyx  # 25 doctests failed

coxeter3 doctests fixes is here (positive review):
http://trac.sagemath.org/ticket/19637