Re: [sage-release] info

[E. Madison Bray]

On Sat, Oct 24, 2020, 10:13 Henri Girard  wrote:

> My sudo -H pip3 install sage got for answer : Requirement already
> satisfied: sage in /usr/lib/python3/dist-packages (9.2b12)
>

For what it's worth, you should almost never `sudo pip install` anything on
Ubuntu, because it can break system packages.

Instead you have several options for installing local copies of packages:

* use `pip install --user`
* create a venv with `python -m venv`, activate the venv, and use `pip
install` in the venv
* create a conda environment and use `pip install` in the activated
environment

>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34a9eGbCcRJPYai-9_3u76_ozsDRXvuAEtQW764Tpq8%3Ddw%40mail.gmail.com.

Re: [sage-release] Sage 9.2.beta8 released

[E. Madison Bray]

On Friday, August 14, 2020 at 1:44:38 PM UTC+2 david@gmail.com wrote:

> Same here on a fresh clone with macOS 10.15.16
>
>
> [dochtml] Building en/constructions.
> [dochtml] 
> [dochtml] [construct] building [html]: targets for 16 source files that 
> are out of date
> [dochtml] [construct] updating environment: [new config] 16 added, 0 
> changed, 0 removed
> ^C[dochtml] Error building the documentation.
> [dochtml] Traceback (most recent call last):
> [dochtml]   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>  
> line 193, in _run_module_as_main
> [dochtml] "__main__", mod_spec)
> [dochtml]   File 
> "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/runpy.py",
>  
> line 85, in _run_code
> [dochtml] exec(code, run_globals)
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
>  
> line 2, in 
> [dochtml] main()
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>  
> line 1721, in main
> [dochtml] builder()
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>  
> line 337, in _wrapper
> [dochtml] build_many(build_other_doc, L)
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/__init__.py",
>  
> line 281, in build_many
> [dochtml] _build_many(target, args, processes=NUM_THREADS)
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>  
> line 263, in build_many
> [dochtml] waited_pid, waited_exitcode = wait_for_one()
> [dochtml]   File 
> "/Users/dcoudert/sage/local/lib/python3.7/site-packages/sage_setup/docbuild/utils.py",
>  
> line 179, in wait_for_one
> [dochtml] pid, sts = os.wait()
> [dochtml]   File "src/cysignals/signals.pyx", line 320, in 
> cysignals.signals.python_check_interrupt
> [dochtml] KeyboardInterrupt
> [dochtml] 
> [dochtml] Note: incremental documentation builds sometimes cause 
> spurious
> [dochtml] error messages. To be certain that these are real errors, run
> [dochtml] "make doc-clean" first and try again.
> make[3]: *** [doc-html] Error 1
> make[2]: *** [all-start] Interrupt: 2
> make[1]: *** [all-start] Interrupt: 2
> make: *** [all] Interrupt: 2
>
>
>
As I noted at [1], this implies that one or more of the docbuilds are 
running some code that hangs forever, so it would help narrow it down by 
finding out what code it's running to cause a hang.  Normally in docbuilds 
the most likely code to run will be some plotting code, so you can try to 
take the plot code present in the relevant documentation pages, run it, and 
see if it hangs.  Chances are if you run it in a single process it might 
*not* hang--frequently this happens only in a forked subprocess.  So you 
can try something like:

from multiprocessing import Process
p = Process(target=)
p.start()

and see if it hangs. I've often found this to be the case with calls to 
np.dot(), which matpotlib uses sometimes to perform various 
transformations, and which in turn often results in a call to a 
multi-threaded OpenBLAS function which are sometimes buggy.

As an aside, I would like to make the parallel doc build code more robust 
to this kind of hang, but it's hard to say exactly what the right solution 
is (I know more or less what the technical solution is, but I mean more the 
UX solution).  Because as far as the docbuild code is concerned, it doesn't 
know that the process is "hung".  It's just taking however long it needs to 
take, and the code will wait for it to finish.  Perhaps we could implement 
some kind of timeout to kill docbuild processes that are taking too long 
(but what should the timeout be)? Or report back to the user exactly which 
docbuilds are still running (like, a log message at some interval) so that 
the user can decide whether or not to take action.

[1] https://trac.sagemath.org/ticket/30351#comment:40 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/2755f337-7bf1-433b-81b1-7a98d1421a8cn%40googlegroups.com.

Re: [sage-release] Sage 9.0.rc0 released

[E. Madison Bray]

On Sat, Dec 28, 2019 at 8:41 PM Samuel Lelièvre
 wrote:
>
> Le sam. 28 déc. 2019 à 02:12, Samuel Lelièvre:
> >
> > Computer, OS, build choices:
> >
> > - iMac, Mid 2015
> > - macOS 10.14.6 Mojave
> > - build for Python 2
> > - build Sage's `gcc` and `openssl` packages
> > - build Sage's Python with its `_ssl` and `_tkinter` modules
> >
> > Running `make testlong` gave 2 failing doctests
> > in the file `src/sage/misc/sageinspect.py`.
> >
> > Running the tests for that file again gave 6 failing doctests.
>
> The key parts seem to be these:
>
> > ModuleNotFoundError: No module named
> > '_Users_lelievre__sage_temp_Ghost_80496_tmp_2caqjln__pyx_0'
>
> where it seems that all "/" and "." in the path
>
>   /Users/lelievre/.sage/temp/Ghost/etc
>
> became underscores. Not sure how to dig into this...

This is intentional: Note that it is says "No module named ..." as
in, it is expecting that to be part of the module *name* (which for
Python modules is typically derived from the filename).  The modules
produced by the cython() function include a mangled version of their
absolute path in the module name itself to ensure that they have
unique module names.

Rather, it looks like it's having some other kind of problem building
Cython modules.  Can you confirm whether or not those examples work
manually?

I've had them fail before in Windows due to fork-related issues, but I
don't know why it would fail on OSX.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34aL1C7EfufF0GpJjneTKVo-30eSs_HsfDaPo8n2ztz03g%40mail.gmail.com.

Re: [sage-release] Sage 9.0.beta9 released

[E. Madison Bray]

On Sun, Dec 8, 2019 at 10:41 PM 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
>
>
> 87c3057957 (tag: 9.0.beta9, trac/develop) Updated SageMath version to 
> 9.0.beta9
> abea10f4ae (origin/develop) Trac #28843: typo ticket: explicitely -> 
> explicitly
> 3988ae0c3b Trac #28841: fix some little details in doc
> d370054b01 Trac #28839: adding a minimal lgtm.yml file
> 9466c95d7f Trac #28835: Remove python3-known-passing.txt and the 
> corresponding parts of the Makefile
> 368a68abad Trac #28830: cleaning the file dlx.py
> 08421c59a1 Trac #28792: SageNB, message about removal
> 6a92dab9a4 Trac #28840: pari 2.11.2
> 1d1e3a3cac Trac #28833: ResourceWarning: unclosed file with SAGE_DEBUG=yes
> d3e64db048 Trac #28818: from gap to libgap in strongly_regular_db
> 6147d1a5c6 Trac #28639: Polyhedron_normaliz: Initialize new cone from both 
> Vrep and Hrep
> f312974943 Trac #28834: Doctesting: don't test SageNB files unless SageNB has 
> been installed
> 9e0670240c Trac #28822: Use assert on a condition that should always be true
> 3814db49b8 Trac #28826: a few typos
> b2254ebec7 Trac #28476: norm returns a negative number
> 71ec07fb58 Trac #28289: Settings in ipython_config.py can cause tests to fail
> f1b8ad8d50 Trac #28825: refresh the file combinat/tuple
> 4c75b8087d Trac #28821: get rid of filter
> 1c63696cfb Trac #28801: Fix ThreeJS script paths for Firefox on Windows
> fb1c004e14 Trac #28541: bug in change_ring for polynomials
> 680649c354 Trac #24398: Document function initialization parameters
> 0a1ddb16a2 Trac #28710: update sagenb to 1.1.3
> 6d8849ca36 Trac #28258: Fork errors in sage.misc.cython doctests
> cf9673bc59 (tag: 9.0.beta8) Updated SageMath version to 9.0.beta8

Can somebody please review the blocker ticket
https://trac.sagemath.org/ticket/28829 ?

It depends on https://trac.sagemath.org/ticket/28832 which now has
positive review.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34aV8%2BLsU_q%2B1H8NFQHEx0fXgYpnmV_YwqwJzPc7HBxmxA%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.0.beta9 released

[E. Madison Bray]

On Mon, Dec 9, 2019 at 5:27 AM Travis Scrimshaw  wrote:
>
> Surprisingly it did work after a distclean. Strange... Sorry for the noise.

Make sure that if `./configure` was re-run that it kept
`--with-python=2`.  There is a bug that if configure gets re-run
needlessly sometimes it doesn't keep the previous flags.  There was
discussion about this in the last release thread.

> On Monday, December 9, 2019 at 1:24:24 PM UTC+10, Travis Scrimshaw wrote:
>>
>> I am unable to build using my Python2 install as it fails at cysignals (it 
>> works on Python3). It might not have been this precise version as I tried 
>> from beta3. I am trying after a distclean, but I don't expect a different 
>> result. I known non-Python3 is a low priority, but I think we should still 
>> try to get this to work. Any thoughts?
>>
>> Best,
>> Travis
>>
>>
>> On Monday, December 9, 2019 at 7:41:25 AM UTC+10, 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
>>>
>>>
>>> 87c3057957 (tag: 9.0.beta9, trac/develop) Updated SageMath version to 
>>> 9.0.beta9
>>> abea10f4ae (origin/develop) Trac #28843: typo ticket: explicitely -> 
>>> explicitly
>>> 3988ae0c3b Trac #28841: fix some little details in doc
>>> d370054b01 Trac #28839: adding a minimal lgtm.yml file
>>> 9466c95d7f Trac #28835: Remove python3-known-passing.txt and the 
>>> corresponding parts of the Makefile
>>> 368a68abad Trac #28830: cleaning the file dlx.py
>>> 08421c59a1 Trac #28792: SageNB, message about removal
>>> 6a92dab9a4 Trac #28840: pari 2.11.2
>>> 1d1e3a3cac Trac #28833: ResourceWarning: unclosed file with SAGE_DEBUG=yes
>>> d3e64db048 Trac #28818: from gap to libgap in strongly_regular_db
>>> 6147d1a5c6 Trac #28639: Polyhedron_normaliz: Initialize new cone from both 
>>> Vrep and Hrep
>>> f312974943 Trac #28834: Doctesting: don't test SageNB files unless SageNB 
>>> has been installed
>>> 9e0670240c Trac #28822: Use assert on a condition that should always be true
>>> 3814db49b8 Trac #28826: a few typos
>>> b2254ebec7 Trac #28476: norm returns a negative number
>>> 71ec07fb58 Trac #28289: Settings in ipython_config.py can cause tests to 
>>> fail
>>> f1b8ad8d50 Trac #28825: refresh the file combinat/tuple
>>> 4c75b8087d Trac #28821: get rid of filter
>>> 1c63696cfb Trac #28801: Fix ThreeJS script paths for Firefox on Windows
>>> fb1c004e14 Trac #28541: bug in change_ring for polynomials
>>> 680649c354 Trac #24398: Document function initialization parameters
>>> 0a1ddb16a2 Trac #28710: update sagenb to 1.1.3
>>> 6d8849ca36 Trac #28258: Fork errors in sage.misc.cython doctests
>>> cf9673bc59 (tag: 9.0.beta8) Updated SageMath version to 9.0.beta8
>>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/003f8ccb-1632-434c-8380-031885ef3f0a%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34bZjZWCUzxAOHooKXEyAzR-WCmd6ZpdNwcg2A08dJ-DaA%40mail.gmail.com.

Re: [sage-release] Sage 9.0.beta8 released

[E. Madison Bray]

On Mon, Dec 2, 2019 at 12:11 PM E. Madison Bray  wrote:
>
> Can I please get a review on https://trac.sagemath.org/ticket/28258 ?
>
> This issue has been holding me up for weeks, making testing difficult.

Thanks Volker (who reviewed).  With that ticket, plus
https://trac.sagemath.org/ticket/28829 (needed to actually
successfully build) all tests pass on Windows+Cygwin on Python 3.
Testing Python 2 next.

> On Mon, Dec 2, 2019 at 12:15 AM 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
> >
> >
> > cf9673bc59 (tag: 9.0.beta8) Updated SageMath version to 9.0.beta8
> > 7b3f429848 Trac #28824: make doc-pdf race condition
> > a6d82755a8 Trac #28823: str_to_bytes in math-readline script for 
> > Mathematica console
> > f5003a0f00 Trac #28809: cleanup 
> > src/sage/combinat/partition_shifting_algebras.py
> > 358d62b1a1 Trac #28790: https in README.md
> > b26d466f03 Trac #28779: Error in "primes_of_bad_reduction" for 
> > DynamicalSystem
> > ec856b746f Trac #28758: random output in a giacpy_sage doctest
> > 873e999025 Trac #28744: py3: add bytes_to_str in Octave interface
> > 953e0a1043 Trac #28733: Reference manual SageTeX incorrect link
> > 4da4603146 Trac #28720: Method is_diagonalizable() should not raise an 
> > error for legitimate inputs
> > 3a018490fb Trac #28680: Three.js: Update documentation examples
> > 5a1cacc884 Trac #28583: unicode_art of Matrix_mod2_dense fails
> > 4e0b121eaf Trac #28820: convert guava interface to libgap
> > 60b65cdfef Trac #28811: add hash for hypergeometric motives
> > 69c463e4c9 Trac #28501: MR35: Honour docbuild limits when building 
> > documentation in Dockerfile
> > 4f68ca865e Trac #28489: py3 + OS X: symbolic/expression.pyx
> > 17cabfa736 Trac #28213: Renaming rational_preperiodic_points() to 
> > all_preperiodic_points()
> > c989b65121 Trac #27784: Characteristic Classes on Vector Bundles
> > b030c58f4e Trac #28170: enhance is_postcritically_finite, 
> > critical_point_portrait, and multiplier_spectra to work over number fields 
> > and finite fields
> > a68601e8f9 Trac #26817: GaloisGroup_subgroup.fixed_field() should always 
> > return an embedding
> > 7a740579e3 Trac #26816: Specify subgroups of Galois groups using generators
> > e95c2c2ef4 Trac #23740: Plotting Julia Sets for General Polynomials
> > c818084a8e Trac #23720: Plotting Mandelbrot Set for General Polynomials
> > f7906eb4ea Trac #28791: Implement Feature without using 
> > sage.misc.cachefunc, sage.structure.unique_representation
> > 9afb930099 Trac #28784: Adding multiple symmetries and multiple 
> > contractions to tensors
> > 4e5d712ad6 Trac #28783: fix opacity for add_condition in mono-coloured 
> > plot3d
> > 671567e777 Trac #28770: Polyhedra coercion of base rings fails for number 
> > fields
> > 910e84cd31 Trac #28769: Scalar field raise AttributeError on 
> > show_identifiers call
> > 6161a34c8b Trac #28764: 2 internet doctest failed in hadamard_matrix.py
> > 692073e6d5 Trac #28763: DIMACS solver not workng with Python3 (7 glucose 
> > optional doctests failed)
> > 954bc2c88b Trac #28751: enhance some calls to "while len"
> > 1ea8e99d76 Trac #28749: some middle-scale cleanup Returns ==> Return in the 
> > doc
> > d8d68e94c6 Trac #28747: further "space:" cleaning outside of combinat
> > f870f83bce Trac #28741: Lattice Polytopes: `compute_facets` does not check 
> > dimension when setting is_reflexive
> > 6c319d2242 Trac #28716: Construction of a vector frame from a family of 
> > vector fields
> > 9ba0c1affb Trac #28627: Lazy OEIS sequences
> > 5975bab92e Trac #27408: Edge view for graphs
> > 307b865431 Trac #28756: py3: fix doctests with gurobi
> > cdda9f70e2 Trac #28759: py3: dot2tex + graphviz doctests failures
> > 1dd55655a1 Trac #28760: py3: internet str vs bytes doctests failures
> > 5dcc2683ed Trac #28761: py3: further fixes for misc
> > 63fb7b0c7d Trac #28805: Remove sagenb from DOC_DEPENDENCIES
> > 9273772c59 Trac #28807: little typo ticket
> > a24bffeeaa Trac #28810: small fix in regular expression for trac warning in 
> > sage/all.py
> > 737eadb5ae Trac #28793: 2 more random doctest failures
> > 7f25a87c16 Trac #28739: cleaning "space:" in the doc of combinat
> > 9d8b63ce88 Trac #28740: fix typo convertable
> > 1246b5a663 Trac #28812: #28795 followup: py2 doctest failure in pynac.pyx
> > e3631b41c5 Trac #28705: Fix con

Re: [sage-release] Re: Sage 9.0.beta8 released

[E. Madison Bray]

On Mon, Dec 2, 2019 at 6:50 AM John H Palmieri  wrote:
>
> Broken with a Python 2 build. Do we care?
>
> In particular, SageNB is not built with Python 2, but the doctester thinks it 
> should be:

We do care: Support for Python 2 is not being dropped yet.  Please
open a blocker ticket.

> ./sage -t -p --all --long --logfile=logs/ptestlong.log
> Running doctests with ID 2019-12-01-19-23-00-d57c8cb5.
> Git branch: develop
> Using --optional=build,dochtml,python2,sage
> Doctesting entire Sage library.
> Traceback (most recent call last):
>   File 
> "/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-9.0.beta8/src/bin/sage-runtests",
>  line 179, in 
> err = DC.run()
>   File 
> "/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-9.0.beta8/local/lib/python2.7/site-packages/sage/doctest/control.py",
>  line 1234, in run
> self.add_files()
>   File 
> "/Users/palmieri/Desktop/Sage_stuff/sage_builds/VANILLA/sage-9.0.beta8/local/lib/python2.7/site-packages/sage/doctest/control.py",
>  line 753, in add_files
> sagenb_loc = working_set.find(Requirement.parse('sagenb')).location
> AttributeError: 'NoneType' object has no attribute 'location'
> make: *** [ptestlong] Error 1
>
>
> On Sunday, December 1, 2019 at 3:15:29 PM UTC-8, 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
>>
>>
>> cf9673bc59 (tag: 9.0.beta8) Updated SageMath version to 9.0.beta8
>> 7b3f429848 Trac #28824: make doc-pdf race condition
>> a6d82755a8 Trac #28823: str_to_bytes in math-readline script for Mathematica 
>> console
>> f5003a0f00 Trac #28809: cleanup 
>> src/sage/combinat/partition_shifting_algebras.py
>> 358d62b1a1 Trac #28790: https in README.md
>> b26d466f03 Trac #28779: Error in "primes_of_bad_reduction" for 
>> DynamicalSystem
>> ec856b746f Trac #28758: random output in a giacpy_sage doctest
>> 873e999025 Trac #28744: py3: add bytes_to_str in Octave interface
>> 953e0a1043 Trac #28733: Reference manual SageTeX incorrect link
>> 4da4603146 Trac #28720: Method is_diagonalizable() should not raise an error 
>> for legitimate inputs
>> 3a018490fb Trac #28680: Three.js: Update documentation examples
>> 5a1cacc884 Trac #28583: unicode_art of Matrix_mod2_dense fails
>> 4e0b121eaf Trac #28820: convert guava interface to libgap
>> 60b65cdfef Trac #28811: add hash for hypergeometric motives
>> 69c463e4c9 Trac #28501: MR35: Honour docbuild limits when building 
>> documentation in Dockerfile
>> 4f68ca865e Trac #28489: py3 + OS X: symbolic/expression.pyx
>> 17cabfa736 Trac #28213: Renaming rational_preperiodic_points() to 
>> all_preperiodic_points()
>> c989b65121 Trac #27784: Characteristic Classes on Vector Bundles
>> b030c58f4e Trac #28170: enhance is_postcritically_finite, 
>> critical_point_portrait, and multiplier_spectra to work over number fields 
>> and finite fields
>> a68601e8f9 Trac #26817: GaloisGroup_subgroup.fixed_field() should always 
>> return an embedding
>> 7a740579e3 Trac #26816: Specify subgroups of Galois groups using generators
>> e95c2c2ef4 Trac #23740: Plotting Julia Sets for General Polynomials
>> c818084a8e Trac #23720: Plotting Mandelbrot Set for General Polynomials
>> f7906eb4ea Trac #28791: Implement Feature without using sage.misc.cachefunc, 
>> sage.structure.unique_representation
>> 9afb930099 Trac #28784: Adding multiple symmetries and multiple contractions 
>> to tensors
>> 4e5d712ad6 Trac #28783: fix opacity for add_condition in mono-coloured plot3d
>> 671567e777 Trac #28770: Polyhedra coercion of base rings fails for number 
>> fields
>> 910e84cd31 Trac #28769: Scalar field raise AttributeError on 
>> show_identifiers call
>> 6161a34c8b Trac #28764: 2 internet doctest failed in hadamard_matrix.py
>> 692073e6d5 Trac #28763: DIMACS solver not workng with Python3 (7 glucose 
>> optional doctests failed)
>> 954bc2c88b Trac #28751: enhance some calls to "while len"
>> 1ea8e99d76 Trac #28749: some middle-scale cleanup Returns ==> Return in the 
>> doc
>> d8d68e94c6 Trac #28747: further "space:" cleaning outside of combinat
>> f870f83bce Trac #28741: Lattice Polytopes: `compute_facets` does not check 
>> dimension when setting is_reflexive
>> 6c319d2242 Trac #28716: Construction of a vector frame from a family of 
>> vector fields
>> 9ba0c1affb Trac #28627: Lazy OEIS sequences
>> 5975bab92e Trac #27408: Edge view for graphs
>> 307b865431 Trac #28756: py3: fix doctests with gurobi
>> cdda9f70e2 Trac #28759: py3: dot2tex + graphviz doctests failures
>> 1dd55655a1 Trac #28760: py3: internet str vs bytes doctests failures
>> 5dcc2683ed Trac #28761: py3: further fixes for misc
>> 63fb7b0c7d Trac #28805: Remove sagenb from DOC_DEPENDENCIES
>> 9273772c59 Trac #28807: little typo ticket
>> a24bffeeaa Trac #28810: small fix in regular expression for trac warning in 
>> sage/all.py
>> 737eadb5ae Trac #28793: 2 more random doctest 

Re: [sage-release] Sage 9.0.beta8 released

[E. Madison Bray]

Can I please get a review on https://trac.sagemath.org/ticket/28258 ?

This issue has been holding me up for weeks, making testing difficult.

On Mon, Dec 2, 2019 at 12:15 AM 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
>
>
> cf9673bc59 (tag: 9.0.beta8) Updated SageMath version to 9.0.beta8
> 7b3f429848 Trac #28824: make doc-pdf race condition
> a6d82755a8 Trac #28823: str_to_bytes in math-readline script for Mathematica 
> console
> f5003a0f00 Trac #28809: cleanup 
> src/sage/combinat/partition_shifting_algebras.py
> 358d62b1a1 Trac #28790: https in README.md
> b26d466f03 Trac #28779: Error in "primes_of_bad_reduction" for DynamicalSystem
> ec856b746f Trac #28758: random output in a giacpy_sage doctest
> 873e999025 Trac #28744: py3: add bytes_to_str in Octave interface
> 953e0a1043 Trac #28733: Reference manual SageTeX incorrect link
> 4da4603146 Trac #28720: Method is_diagonalizable() should not raise an error 
> for legitimate inputs
> 3a018490fb Trac #28680: Three.js: Update documentation examples
> 5a1cacc884 Trac #28583: unicode_art of Matrix_mod2_dense fails
> 4e0b121eaf Trac #28820: convert guava interface to libgap
> 60b65cdfef Trac #28811: add hash for hypergeometric motives
> 69c463e4c9 Trac #28501: MR35: Honour docbuild limits when building 
> documentation in Dockerfile
> 4f68ca865e Trac #28489: py3 + OS X: symbolic/expression.pyx
> 17cabfa736 Trac #28213: Renaming rational_preperiodic_points() to 
> all_preperiodic_points()
> c989b65121 Trac #27784: Characteristic Classes on Vector Bundles
> b030c58f4e Trac #28170: enhance is_postcritically_finite, 
> critical_point_portrait, and multiplier_spectra to work over number fields 
> and finite fields
> a68601e8f9 Trac #26817: GaloisGroup_subgroup.fixed_field() should always 
> return an embedding
> 7a740579e3 Trac #26816: Specify subgroups of Galois groups using generators
> e95c2c2ef4 Trac #23740: Plotting Julia Sets for General Polynomials
> c818084a8e Trac #23720: Plotting Mandelbrot Set for General Polynomials
> f7906eb4ea Trac #28791: Implement Feature without using sage.misc.cachefunc, 
> sage.structure.unique_representation
> 9afb930099 Trac #28784: Adding multiple symmetries and multiple contractions 
> to tensors
> 4e5d712ad6 Trac #28783: fix opacity for add_condition in mono-coloured plot3d
> 671567e777 Trac #28770: Polyhedra coercion of base rings fails for number 
> fields
> 910e84cd31 Trac #28769: Scalar field raise AttributeError on show_identifiers 
> call
> 6161a34c8b Trac #28764: 2 internet doctest failed in hadamard_matrix.py
> 692073e6d5 Trac #28763: DIMACS solver not workng with Python3 (7 glucose 
> optional doctests failed)
> 954bc2c88b Trac #28751: enhance some calls to "while len"
> 1ea8e99d76 Trac #28749: some middle-scale cleanup Returns ==> Return in the 
> doc
> d8d68e94c6 Trac #28747: further "space:" cleaning outside of combinat
> f870f83bce Trac #28741: Lattice Polytopes: `compute_facets` does not check 
> dimension when setting is_reflexive
> 6c319d2242 Trac #28716: Construction of a vector frame from a family of 
> vector fields
> 9ba0c1affb Trac #28627: Lazy OEIS sequences
> 5975bab92e Trac #27408: Edge view for graphs
> 307b865431 Trac #28756: py3: fix doctests with gurobi
> cdda9f70e2 Trac #28759: py3: dot2tex + graphviz doctests failures
> 1dd55655a1 Trac #28760: py3: internet str vs bytes doctests failures
> 5dcc2683ed Trac #28761: py3: further fixes for misc
> 63fb7b0c7d Trac #28805: Remove sagenb from DOC_DEPENDENCIES
> 9273772c59 Trac #28807: little typo ticket
> a24bffeeaa Trac #28810: small fix in regular expression for trac warning in 
> sage/all.py
> 737eadb5ae Trac #28793: 2 more random doctest failures
> 7f25a87c16 Trac #28739: cleaning "space:" in the doc of combinat
> 9d8b63ce88 Trac #28740: fix typo convertable
> 1246b5a663 Trac #28812: #28795 followup: py2 doctest failure in pynac.pyx
> e3631b41c5 Trac #28705: Fix conversion of Booleans in interfaces
> 075c09c577 Trac #28694: rich comparison for matrices
> efe7f5594e Trac #28614: CombinatorialPolyhedron: length_* to n_*
> d8818f1fd9 Trac #27154: speed_up_Burge
> c585682116 Trac #25701: Implement Sieve algorithm for product_projective space
> 695306e10b Trac #22380: Upgrade to cvxopt 1.2.x
> d48a21c149 (tag: 9.0.beta7) Updated SageMath version to 9.0.beta7
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/9bccedc9-0b7c-44ef-8dae-955a73988563%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving 

Re: [sage-release] Re: Sage 9.0.beta6 released

[E. Madison Bray]

On Tue, Nov 19, 2019 at 2:55 PM E. Madison Bray  wrote:
>
> On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé  wrote:
> >
> >
> >
> >
> > The first try at running make gives me this:
> >
> >
> > [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « 
> > /home/slabbe/GitBox/sage/src »
> > [sagelib-9.0.beta6] cd . && export\
> > [sagelib-9.0.beta6] SAGE_ROOT=/doesnotexist 
> >   \
> > [sagelib-9.0.beta6] SAGE_SRC=/doesnotexist  
> >   \
> > [sagelib-9.0.beta6] SAGE_SRC_ROOT=/doesnotexist 
> >   \
> > [sagelib-9.0.beta6] SAGE_DOC_SRC=/doesnotexist  
> >   \
> > [sagelib-9.0.beta6] SAGE_BUILD_DIR=/doesnotexist
> >   \
> > [sagelib-9.0.beta6] SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs   
> >  \
> > [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build install
> > [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne 130 : 
> > cd: /doesnotexist: Aucun fichier ou dossier de ce type
> > [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment variable:
> > [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist
> > [sagelib-9.0.beta6] New SAGE_ROOT=
> > [sagelib-9.0.beta6] Traceback (most recent call last):
> > [sagelib-9.0.beta6]   File "setup.py", line 22, in 
> > [sagelib-9.0.beta6] import fpickle_setup
> > [sagelib-9.0.beta6]   File "/home/slabbe/GitBox/sage/src/fpickle_setup.py", 
> > line 8, in 
> > [sagelib-9.0.beta6] from six.moves import copyreg
> > [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six'
> > [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » a 
> > échouée
> > [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1
> > [sagelib-9.0.beta6] make[4] : on quitte le répertoire « 
> > /home/slabbe/GitBox/sage/src »
> > [sagelib-9.0.beta6]
> > [sagelib-9.0.beta6] real0m0.049s
> > [sagelib-9.0.beta6] user0m0.032s
> > [sagelib-9.0.beta6] sys0m0.012s
> > Makefile:1987 : la recette pour la cible « sagelib » a échouée
> > make[3]: *** [sagelib] Erreur 2
> > make[3] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make »
> > Makefile:1848 : la recette pour la cible « all-start » a échouée
> > make[2]: *** [all-start] Erreur 2
> > make[2] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make »
> >
> > real0m0.208s
> > user0m0.148s
> > sys0m0.016s
> > ***
> > Error building Sage.
> >
> > The following package(s) may have failed to build (not necessarily
> > during this run of 'make all-start'):
> >
> > The build directory may contain configuration files and other potentially
> > helpful information. WARNING: if you now run 'make' again, the build
> > directory will, by default, be deleted. Set the environment variable
> > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
> IMO this does appear to be a bug though.  If you have an existing
> Python 2 build of Sage it should *not* break just because the default
> has changed to Python 3.  It appears something is trying to run the
> fpickle_setup.py script (whatever that is) with python3 even if it's a
> python2 build of Sage.

Nevermind--the real issue is the opposite of what I wrote two posts
ago.  If you have a python2 build of Sage and you want to keep it as
python2 you need to do a `./configure --with-python=2`.  It's kind of
annoying that this is not preserved (I'm a little confused that it
isn't, since I thought that was the point of having config.status...)

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34a%2BQ9tWiEMN325KKxfdYoDXj3XF-QEmLxvWh5kQqP1xyQ%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.0.beta6 released

[E. Madison Bray]

On Mon, Nov 18, 2019 at 3:51 PM Sébastien Labbé  wrote:
>
>
>
>
> The first try at running make gives me this:
>
>
> [sagelib-9.0.beta6] make[4] : on entre dans le répertoire « 
> /home/slabbe/GitBox/sage/src »
> [sagelib-9.0.beta6] cd . && export\
> [sagelib-9.0.beta6] SAGE_ROOT=/doesnotexist   
> \
> [sagelib-9.0.beta6] SAGE_SRC=/doesnotexist
> \
> [sagelib-9.0.beta6] SAGE_SRC_ROOT=/doesnotexist   
> \
> [sagelib-9.0.beta6] SAGE_DOC_SRC=/doesnotexist
> \
> [sagelib-9.0.beta6] SAGE_BUILD_DIR=/doesnotexist  
> \
> [sagelib-9.0.beta6] SAGE_PKGS=/home/slabbe/GitBox/sage/build/pkgs 
>\
> [sagelib-9.0.beta6] && sage-python -u setup.py --no-user-cfg build install
> [sagelib-9.0.beta6] /home/slabbe/GitBox/sage/src/bin/sage-env: ligne 130 : 
> cd: /doesnotexist: Aucun fichier ou dossier de ce type
> [sagelib-9.0.beta6] Warning: overwriting SAGE_ROOT environment variable:
> [sagelib-9.0.beta6] Old SAGE_ROOT=/doesnotexist
> [sagelib-9.0.beta6] New SAGE_ROOT=
> [sagelib-9.0.beta6] Traceback (most recent call last):
> [sagelib-9.0.beta6]   File "setup.py", line 22, in 
> [sagelib-9.0.beta6] import fpickle_setup
> [sagelib-9.0.beta6]   File "/home/slabbe/GitBox/sage/src/fpickle_setup.py", 
> line 8, in 
> [sagelib-9.0.beta6] from six.moves import copyreg
> [sagelib-9.0.beta6] ModuleNotFoundError: No module named 'six'
> [sagelib-9.0.beta6] Makefile:33 : la recette pour la cible « sage » a échouée
> [sagelib-9.0.beta6] make[4]: *** [sage] Erreur 1
> [sagelib-9.0.beta6] make[4] : on quitte le répertoire « 
> /home/slabbe/GitBox/sage/src »
> [sagelib-9.0.beta6]
> [sagelib-9.0.beta6] real0m0.049s
> [sagelib-9.0.beta6] user0m0.032s
> [sagelib-9.0.beta6] sys0m0.012s
> Makefile:1987 : la recette pour la cible « sagelib » a échouée
> make[3]: *** [sagelib] Erreur 2
> make[3] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make »
> Makefile:1848 : la recette pour la cible « all-start » a échouée
> make[2]: *** [all-start] Erreur 2
> make[2] : on quitte le répertoire « /home/slabbe/GitBox/sage/build/make »
>
> real0m0.208s
> user0m0.148s
> sys0m0.016s
> ***
> Error building Sage.
>
> The following package(s) may have failed to build (not necessarily
> during this run of 'make all-start'):
>
> The build directory may contain configuration files and other potentially
> helpful information. WARNING: if you now run 'make' again, the build
> directory will, by default, be deleted. Set the environment variable
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

IMO this does appear to be a bug though.  If you have an existing
Python 2 build of Sage it should *not* break just because the default
has changed to Python 3.  It appears something is trying to run the
fpickle_setup.py script (whatever that is) with python3 even if it's a
python2 build of Sage.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34Zr2Een8%2Bvoj%2Bim%3DpP6o_Xm4P6BFZarZ1uDzXa8rc58Wg%40mail.gmail.com.

Re: [sage-release] Re: Sage 9.0.beta6 released

[E. Madison Bray]

On Mon, Nov 18, 2019 at 9:31 PM darwin doppelganger  wrote:
>
> I did a "make distclean" followed by "make" on my Mac OSX 10.14.6, Xcode 
> 11.2.1 and the build completed successfully:

It's not even necessary to do a full `make distclean`.  Instead you
have to manually reconfigure your build to use --with-python=3 like

$ ./configure --with-python=3

*then*

$ make

>> [2019-11-18 14:22:10] SageMath version 9.0.beta6, Release Date: 2019-11-18
>> Yes, Sage starts.
>> real257m11.634s
>> user280m20.436s
>> sys 31m35.438s
>> Sage build/upgrade complete!
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/3bc5756c-679b-4525-be49-b587b5151de1%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34ZwHZvxy3gNCWjvY9hnfnPam23watd8%2BtUw2aUpomnz7g%40mail.gmail.com.

Re: [sage-release] Sage 9.0.beta5 released

[E. Madison Bray]

On Wed, Nov 13, 2019 at 6:23 PM E. Madison Bray  wrote:
>
> On Wed, Nov 13, 2019 at 6:15 PM E. Madison Bray  wrote:
> >
> > Testing this on Windows + Python 3 for the first time in a while.
> > During the docbuild it crashes while generating one of the plots, with
> > some call to maxima resulting in:
> >
> > RuntimeError: ECL says: #
> >
> > I'll see if I can get this in any other context.  Has anyone else seen
> > problems like this on Python 3?
>
> How to reproduce:
>
> sage: f = piecewise([((0,pi/2), -1), ((pi/2,pi), 2)])
> sage: s5 = f.fourier_series_partial_sum(5)

False alarm, I guess.  I did a `./sage -f ecl && make build` and now
everything works.  Slightly disconcerting, but possibly attributable
to reusing an old Python 3 build that was left in a dubious state.

I'm very impressed, and congratulations to Frédéric et al. for getting
things this far! I'm sorry I couldn't have been of more help in the
final push.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34ao%2Bg1vUb_nrUX8X5Srb6jETJa_82BnB6gvgu5mEkvhng%40mail.gmail.com.

Re: [sage-release] Sage 9.0.beta5 released

[E. Madison Bray]

On Wed, Nov 13, 2019 at 6:15 PM E. Madison Bray  wrote:
>
> Testing this on Windows + Python 3 for the first time in a while.
> During the docbuild it crashes while generating one of the plots, with
> some call to maxima resulting in:
>
> RuntimeError: ECL says: #
>
> I'll see if I can get this in any other context.  Has anyone else seen
> problems like this on Python 3?

How to reproduce:

sage: f = piecewise([((0,pi/2), -1), ((pi/2,pi), 2)])
sage: s5 = f.fourier_series_partial_sum(5)
---
RuntimeError  Traceback (most recent call last)
 in ()
> 1 s5 = f.fourier_series_partial_sum(Integer(5))

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/expression.pyx
in sage.symbolic.expression._eval_on_operands.new_f
(build/cythonized/sage/symbolic/expression.cpp:67434)()
  12688 new_args = list(ex._unpack_operands())
  12689 new_args.extend(args)
> 12690 return f(ex, *new_args, **kwds)
  12691 return new_f
  12692

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/functions/piecewise.py
in fourier_series_partial_sum(self, parameters, variable, N, L)
   1347 L = (self.domain().sup() - self.domain().inf()) / 2
   1348 x = self.default_variable()
-> 1349 a0 = self.fourier_series_cosine_coefficient(0, L)
   1350 result = a0/2 +
sum([(self.fourier_series_cosine_coefficient(n, L)*cos(n*pi*x/L) +
   1351
self.fourier_series_sine_coefficient(n, L)*sin(n*pi*x/L))

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/expression.pyx
in sage.symbolic.expression._eval_on_operands.new_f
(build/cythonized/sage/symbolic/expression.cpp:67434)()
  12688 new_args = list(ex._unpack_operands())
  12689 new_args.extend(args)
> 12690 return f(ex, *new_args, **kwds)
  12691 return new_f
  12692

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/functions/piecewise.py
in fourier_series_cosine_coefficient(self, parameters, variable, n, L)
   1179 a = interval.lower()
   1180 b = interval.upper()
-> 1181 result += (f*cos(pi*x*n/L)).integrate(x, a, b)
   1182 return SR(result/L0).simplify_trig()
   1183

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/expression.pyx
in sage.symbolic.expression.Expression.integral
(build/cythonized/sage/symbolic/expression.cpp:64542)()
  12370 R = ring.SR
  12371 return R(integral(f, v, a, b, **kwds))
> 12372 return integral(self, *args, **kwds)
  12373
  12374 integrate = integral

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/integration/integral.py
in integrate(expression, v, a, b, algorithm, hold)
921 return indefinite_integral(expression, v, hold=hold)
922 else:
--> 923 return definite_integral(expression, v, a, b, hold=hold)
924
925

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/function.pyx
in sage.symbolic.function.BuiltinFunction.__call__
(build/cythonized/sage/symbolic/function.cpp:12262)()
   1025 res = self._evalf_try_(*args)
   1026 if res is None:
-> 1027 res = super(BuiltinFunction, self).__call__(
   1028 *args, coerce=coerce, hold=hold)
   1029

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/function.pyx
in sage.symbolic.function.Function.__call__
(build/cythonized/sage/symbolic/function.cpp:6938)()
484 for i from 0 <= i < len(args):
485 vec.push_back((args[i])._gobj)
--> 486 res = g_function_evalv(self._serial, vec, hold)
487 elif self._nargs == 1:
488 res = g_function_eval1(self._serial,

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/function.pyx
in sage.symbolic.function.BuiltinFunction._evalf_or_eval_
(build/cythonized/sage/symbolic/function.cpp:13412)()
   1113 res = self._evalf_try_(*args)
   1114 if res is None:
-> 1115 return self._eval0_(*args)
   1116 else:
   1117 return res

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/integration/integral.py
in _eval_(self, f, x, a, b)
195 for integrator in self.integrators:
196 try:
--> 197 A = integrator(*args)
198 except (NotImplementedError, TypeError):
199 pass

/home/embray/src/sagemath/sage-python3/local/lib/python3.7/site-packages/sage/symbolic/integration/external.py
in maxima_integrato

Re: [sage-release] Sage 9.0.beta5 released

[E. Madison Bray]

Testing this on Windows + Python 3 for the first time in a while.
During the docbuild it crashes while generating one of the plots, with
some call to maxima resulting in:

RuntimeError: ECL says: #

I'll see if I can get this in any other context.  Has anyone else seen
problems like this on Python 3?

On Tue, Nov 12, 2019 at 10:45 PM 'Justin C. Walker' via sage-release
 wrote:
>
>
>
> > On Nov 10, 2019, at 15:59 , 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 a fresh clone of the develop tree on three macOS platforms: 
> 10.11.6 (mid-2015 MBP, Quad-core Core i7), 10.13.6 (2017 iMac Pro, 18-core 
> Xeon W), 10.14.6 (2017 MBP, Quad-core Core i7).  All builds completed w/o 
> problems.
>
> Testing (‘ptestlong’) went as follows:
>
> 10.11.6: all tests passed!
> 10.13.6: one failure, good ol’ polynomials.pyx.  Stand-alone runs passed.
> 10.14.6: all tests passed!
>
> Justin
>
> --
> Justin C. Walker, Curmudgeon at Large
> Institute for the Absorption of Federal Funds
> ---
> I'm beginning to like the cut of his jibberish.
> ---
>
>
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/65C6ED2B-2CB3-4340-98D0-A3D90333092C%40mac.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34Y3t40gevL_6WkSj0duV4BAhNjNyVyxfxPbjuA1xyUUyA%40mail.gmail.com.

Re: [sage-release] Sage 8.9 released

[E. Madison Bray]

On Mon, Oct 7, 2019 at 6:00 PM E. Madison Bray  wrote:
>
> On Mon, Oct 7, 2019 at 5:57 PM E. Madison Bray  wrote:
> >
> > When building from scratch on Cygwin I am getting some errors related
> > to OMP-related symbols being missing when linking a Sage module that
> > uses fflas-ffpack; specifically sage.libs.linbox_flint_interface:
> >
> > [sagelib-8.9] g++ -shared -Wl,--enable-auto-image-base
> > -L/opt/sagemath-8.9/local/lib -Wl,-rpath,/opt/sagemath-8.9/local/lib
> > -L/opt/sagemath-8.9/local/lib -Wl,-rpath,/opt/sagemath-8.9/local/lib
> > build/temp.cygwin-3.0.7-x86_64-2.7/build/cythonized/sage/libs/linbox/linbox_flint_interface.o
> > -L/opt/sagemath-8.9/local/lib
> > -L/opt/sagemath-8.9/local/lib/python2.7/config
> > -L/opt/sagemath-8.9/local/lib -llinbox -lntl -liml -lfflas -lffpack
> > -lgivaro -lblas -lflint -lmpfr -lgmp -lgmpxx -lstdc++ -lpython2.7 -o
> > build/lib.cygwin-3.0.7-x86_64-2.7/sage/libs/linbox/linbox_flint_interface.dll
> > [sagelib-8.9] 
> > build/temp.cygwin-3.0.7-x86_64-2.7/build/cythonized/sage/libs/linbox/linbox_flint_interface.o:
> > In function `FFPACK::rns_double::init(unsigned long, unsigned long,
> > double*, unsigned long, Givaro::Integer const*, unsigned long,
> > unsigned long, bool) const [clone ._omp_fn.0]':
> > [sagelib-8.9] 
> > /opt/sagemath-8.9/local/include/fflas-ffpack/field/rns-double.inl:95:
> > undefined reference to `GOMP_loop_ull_runtime_start'
> >
> > it goes on like that for several related errors.  I've never seen this
> > one before.  This is with gcc 7.4.0.
> >
> > This was doing a build from scratch for a release, in a clean Cygwin
> > install, so I'm not sure where the difference is.  One thing I can
> > see, comparing to a previous build log of my development sage from one
> > of the 8.9 release candidates (with fflas-ffpack 2.4.3) that that
> > module was compiled *without* -fopenmp, whereas on my clean build it
> > is passing -fopenmp and I'm not sure where the difference is coming
> > from.
>
> Ahah, I can also see that in my development build, configuring
> fflas-ffpack output:
>
> checking for OpenMP... no
>
> whereas on my release build it has
>
> checking for OpenMP... yes
>
>
> For now I don't need or care about OpenMP support, as I have not
> tested that at all on Windows.  I just need to figure out why that
> flag is being forcibly set...

It appears we used to configure fflas-ffpack with --disable-openmp,
however this ticket removed that:
https://trac.sagemath.org/ticket/27444 without bumping the package
patch level.
It also didn't remove the comment about disabling OpenMP support, even
though it no longer disables it.  I'm not sure it make sense to make
that the default; perhaps there should be a global config flag for
whether or not Sage and its dependencies should be built with OpenMP
support.



> > On Mon, Sep 30, 2019 at 1:19 AM Volker Braun  wrote:
> > >
> > > The "master" git branch has been updated to Sage-8.9. 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
> > >
> > > There was no change over 8.9.rc1
> > >
> > > --
> > > 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+unsubscr...@googlegroups.com.
> > > To view this discussion on the web visit 
> > > https://groups.google.com/d/msgid/sage-release/ea48d604-eff9-4b8c-ab44-a0929a7e99f9%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34aDCyYgi6Q6aD1BixY0g-cf1G_1J8sZcbu58YmwcuHsYw%40mail.gmail.com.

Re: [sage-release] Sage 8.9 released

[E. Madison Bray]

On Mon, Oct 7, 2019 at 5:57 PM E. Madison Bray  wrote:
>
> When building from scratch on Cygwin I am getting some errors related
> to OMP-related symbols being missing when linking a Sage module that
> uses fflas-ffpack; specifically sage.libs.linbox_flint_interface:
>
> [sagelib-8.9] g++ -shared -Wl,--enable-auto-image-base
> -L/opt/sagemath-8.9/local/lib -Wl,-rpath,/opt/sagemath-8.9/local/lib
> -L/opt/sagemath-8.9/local/lib -Wl,-rpath,/opt/sagemath-8.9/local/lib
> build/temp.cygwin-3.0.7-x86_64-2.7/build/cythonized/sage/libs/linbox/linbox_flint_interface.o
> -L/opt/sagemath-8.9/local/lib
> -L/opt/sagemath-8.9/local/lib/python2.7/config
> -L/opt/sagemath-8.9/local/lib -llinbox -lntl -liml -lfflas -lffpack
> -lgivaro -lblas -lflint -lmpfr -lgmp -lgmpxx -lstdc++ -lpython2.7 -o
> build/lib.cygwin-3.0.7-x86_64-2.7/sage/libs/linbox/linbox_flint_interface.dll
> [sagelib-8.9] 
> build/temp.cygwin-3.0.7-x86_64-2.7/build/cythonized/sage/libs/linbox/linbox_flint_interface.o:
> In function `FFPACK::rns_double::init(unsigned long, unsigned long,
> double*, unsigned long, Givaro::Integer const*, unsigned long,
> unsigned long, bool) const [clone ._omp_fn.0]':
> [sagelib-8.9] 
> /opt/sagemath-8.9/local/include/fflas-ffpack/field/rns-double.inl:95:
> undefined reference to `GOMP_loop_ull_runtime_start'
>
> it goes on like that for several related errors.  I've never seen this
> one before.  This is with gcc 7.4.0.
>
> This was doing a build from scratch for a release, in a clean Cygwin
> install, so I'm not sure where the difference is.  One thing I can
> see, comparing to a previous build log of my development sage from one
> of the 8.9 release candidates (with fflas-ffpack 2.4.3) that that
> module was compiled *without* -fopenmp, whereas on my clean build it
> is passing -fopenmp and I'm not sure where the difference is coming
> from.

Ahah, I can also see that in my development build, configuring
fflas-ffpack output:

checking for OpenMP... no

whereas on my release build it has

checking for OpenMP... yes


For now I don't need or care about OpenMP support, as I have not
tested that at all on Windows.  I just need to figure out why that
flag is being forcibly set...


> On Mon, Sep 30, 2019 at 1:19 AM Volker Braun  wrote:
> >
> > The "master" git branch has been updated to Sage-8.9. 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
> >
> > There was no change over 8.9.rc1
> >
> > --
> > 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+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-release/ea48d604-eff9-4b8c-ab44-a0929a7e99f9%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34YKKrE2eudAi2BgkMj%2BekzTB5gPrws5jhK6%3DntfN%2Bh37g%40mail.gmail.com.

Re: [sage-release] Sage 8.9 released

[E. Madison Bray]

When building from scratch on Cygwin I am getting some errors related
to OMP-related symbols being missing when linking a Sage module that
uses fflas-ffpack; specifically sage.libs.linbox_flint_interface:

[sagelib-8.9] g++ -shared -Wl,--enable-auto-image-base
-L/opt/sagemath-8.9/local/lib -Wl,-rpath,/opt/sagemath-8.9/local/lib
-L/opt/sagemath-8.9/local/lib -Wl,-rpath,/opt/sagemath-8.9/local/lib
build/temp.cygwin-3.0.7-x86_64-2.7/build/cythonized/sage/libs/linbox/linbox_flint_interface.o
-L/opt/sagemath-8.9/local/lib
-L/opt/sagemath-8.9/local/lib/python2.7/config
-L/opt/sagemath-8.9/local/lib -llinbox -lntl -liml -lfflas -lffpack
-lgivaro -lblas -lflint -lmpfr -lgmp -lgmpxx -lstdc++ -lpython2.7 -o
build/lib.cygwin-3.0.7-x86_64-2.7/sage/libs/linbox/linbox_flint_interface.dll
[sagelib-8.9] 
build/temp.cygwin-3.0.7-x86_64-2.7/build/cythonized/sage/libs/linbox/linbox_flint_interface.o:
In function `FFPACK::rns_double::init(unsigned long, unsigned long,
double*, unsigned long, Givaro::Integer const*, unsigned long,
unsigned long, bool) const [clone ._omp_fn.0]':
[sagelib-8.9] 
/opt/sagemath-8.9/local/include/fflas-ffpack/field/rns-double.inl:95:
undefined reference to `GOMP_loop_ull_runtime_start'

it goes on like that for several related errors.  I've never seen this
one before.  This is with gcc 7.4.0.

This was doing a build from scratch for a release, in a clean Cygwin
install, so I'm not sure where the difference is.  One thing I can
see, comparing to a previous build log of my development sage from one
of the 8.9 release candidates (with fflas-ffpack 2.4.3) that that
module was compiled *without* -fopenmp, whereas on my clean build it
is passing -fopenmp and I'm not sure where the difference is coming
from.

On Mon, Sep 30, 2019 at 1:19 AM Volker Braun  wrote:
>
> The "master" git branch has been updated to Sage-8.9. 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
>
> There was no change over 8.9.rc1
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/ea48d604-eff9-4b8c-ab44-a0929a7e99f9%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34aMMVm9rUt057Vew3ON6VBcWQSva5zm3Hx%3D-StOeubSbw%40mail.gmail.com.

Re: [sage-release] Sage 8.9.beta9 released

[E. Madison Bray]

On Fri, Sep 6, 2019 at 11:36 AM E. Madison Bray  wrote:
>
> Consistently getting a test failure on Cygwin related to some oddity in GAP:
>
> sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py
> **
> File "src/sage/tests/cmdline.py", line 535, in
> sage.tests.cmdline.test_executable
> Failed example:
> out
> Expected:
> '120\n'
> Got:
> "you can 'quit;' to quit to outer loop, or\nyou can 'return;' to 
> continue\n"
> **
> File "src/sage/tests/cmdline.py", line 537, in
> sage.tests.cmdline.test_executable
> Failed example:
> err.replace('gap: halving pool size.', '').strip()
> Expected:
> ''
> Got:
> 'Error,  must not contain \'\\\' or \':\' at
> /home/embray/src/sagemath/sage/local/share/gap/lib/files.gi:53 called
> from\nfunc( C[i] ) at
> /home/embray/src/sagemath/sage/local/share/gap/lib/coll.gi:665 called
> from\nList( GAPInfo.DirectoriesSystemPrograms, Directory \n ) at
> /home/embray/src/sagemath/sage/local/share/gap/lib/files.gd:420 called
> from\n(  )\n called
> from read-eval loop at
> /home/embray/src/sagemath/sage/local/share/gap/pkg/alnuth-3.1.1/defs.g:10\nbrk>
> 120\nbrk>'
> **
> 1 item had failures:
>2 of 251 in sage.tests.cmdline.test_executable
> [250 tests, 2 failures, 273.09 s]
> --
> sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py  # 2 doctests 
> failed
> --
>
> Can't be sure yet that it isn't just a weird, localized issue in my
> installation.  Will investigate.

Yes, that's all it was.  I had a PATH entry with a \ in it, thanks to
conda still being a bit buggy on Cygwin :)  Conversely, I don't think
GAP should blow up in this case either.  So, two issues to file
\o/


> On Tue, Sep 3, 2019 at 1:22 AM 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
> >
> >
> > bdf4b23d74 (trac/develop, tag: 8.9.beta9) Updated SageMath version to 
> > 8.9.beta9
> > c631202c12 Trac #28411: refresh the prompt in the installation guide
> > 45482b13f0 Trac #28387: Implement function that returns the balanced digit 
> > representation of an integer
> > 4454ffec0d Trac #28384: py2: UnicodeDecodeError in doctest framework 
> > exception handling
> > 0c8192c3de Trac #28366: Lattice precision timing test fails on Windows 7 
> > due to low-ish clock resolution
> > 5e1b351a89 Trac #28274: EnumeratedFamily should use integers as keys
> > ec9715bb88 Trac #28172: Profile of a Finite Permutation Group
> > dcf58df8b5 Trac #28154: SciPy: patch for missing coding lines in some 
> > source files
> > 82d75fd335 Trac #27917: Standardize doctest headers
> > 04d5aab185 Trac #25817: RuntimeError: Encountered operator mismatch in 
> > maxima-to-sr translation, integrate
> > 45314bcbcf Trac #23639: Strange errors with roots() of polynomials over 
> > polynomial rings
> > f29cee985f Trac #28419: new pyflakes miscellanous cleanup
> > 77bddf472a Trac #28417: removed deprecated stuff in integer_mod
> > c565a3aa0a Trac #28412: upgrade Pynac to 0.7.26
> > 2e47b34ab8 Trac #28408: fixing a few invalid escape sequences
> > 877d26294b Trac #28407: py3: fix quantum_group_gap and graph_latex
> > 3db8be3dc0 Trac #28399: remove deprecated things in integer.pyx
> > 6a837c5ea6 Trac #27818: Meet-subsemilattice for lattices
> > 2920f66a0e Trac #27798: Add `backend` option to associahedron and flow 
> > polytope
> > 98f3199887 Trac #27587: Follow up to #25680: Fix tempfile handling in 
> > doctests
> > 0719be21c2 Trac #27473: Matrix inversion fails over a Laurent series ring
> > 842a3dcd41 Trac #27444: Expose multithreaded fflas-ffpack features
> > cee95e6b38 Trac #28404: Sign of hypergeometric motives is sometimes wrong
> > af8bf5ead8 Trac #28400: fixing a few roles
> > 1cdf4955c6 Trac #28398: _richcmp_ for quaternion algebra elements
> > abb2397287 Trac #28397: fix some wrong doctests that were not run
> > 2465a9e494 Trac #28396: faster Möbius matrix for Hasse diagrams
> > 4b4b5bf81b Trac #28395: Bug in is_weil_polynomial
> > 77466c5716 Trac #28393: add self-tests for polymake
> > a7f0a353e5 Trac #28391: dependencies file for jupymake
> >

Re: [sage-release] Sage 8.9.beta9 released

[E. Madison Bray]

Consistently getting a test failure on Cygwin related to some oddity in GAP:

sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py
**
File "src/sage/tests/cmdline.py", line 535, in
sage.tests.cmdline.test_executable
Failed example:
out
Expected:
'120\n'
Got:
"you can 'quit;' to quit to outer loop, or\nyou can 'return;' to continue\n"
**
File "src/sage/tests/cmdline.py", line 537, in
sage.tests.cmdline.test_executable
Failed example:
err.replace('gap: halving pool size.', '').strip()
Expected:
''
Got:
'Error,  must not contain \'\\\' or \':\' at
/home/embray/src/sagemath/sage/local/share/gap/lib/files.gi:53 called
from\nfunc( C[i] ) at
/home/embray/src/sagemath/sage/local/share/gap/lib/coll.gi:665 called
from\nList( GAPInfo.DirectoriesSystemPrograms, Directory \n ) at
/home/embray/src/sagemath/sage/local/share/gap/lib/files.gd:420 called
from\n(  )\n called
from read-eval loop at
/home/embray/src/sagemath/sage/local/share/gap/pkg/alnuth-3.1.1/defs.g:10\nbrk>
120\nbrk>'
**
1 item had failures:
   2 of 251 in sage.tests.cmdline.test_executable
[250 tests, 2 failures, 273.09 s]
--
sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py  # 2 doctests failed
--

Can't be sure yet that it isn't just a weird, localized issue in my
installation.  Will investigate.

On Tue, Sep 3, 2019 at 1:22 AM 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
>
>
> bdf4b23d74 (trac/develop, tag: 8.9.beta9) Updated SageMath version to 
> 8.9.beta9
> c631202c12 Trac #28411: refresh the prompt in the installation guide
> 45482b13f0 Trac #28387: Implement function that returns the balanced digit 
> representation of an integer
> 4454ffec0d Trac #28384: py2: UnicodeDecodeError in doctest framework 
> exception handling
> 0c8192c3de Trac #28366: Lattice precision timing test fails on Windows 7 due 
> to low-ish clock resolution
> 5e1b351a89 Trac #28274: EnumeratedFamily should use integers as keys
> ec9715bb88 Trac #28172: Profile of a Finite Permutation Group
> dcf58df8b5 Trac #28154: SciPy: patch for missing coding lines in some source 
> files
> 82d75fd335 Trac #27917: Standardize doctest headers
> 04d5aab185 Trac #25817: RuntimeError: Encountered operator mismatch in 
> maxima-to-sr translation, integrate
> 45314bcbcf Trac #23639: Strange errors with roots() of polynomials over 
> polynomial rings
> f29cee985f Trac #28419: new pyflakes miscellanous cleanup
> 77bddf472a Trac #28417: removed deprecated stuff in integer_mod
> c565a3aa0a Trac #28412: upgrade Pynac to 0.7.26
> 2e47b34ab8 Trac #28408: fixing a few invalid escape sequences
> 877d26294b Trac #28407: py3: fix quantum_group_gap and graph_latex
> 3db8be3dc0 Trac #28399: remove deprecated things in integer.pyx
> 6a837c5ea6 Trac #27818: Meet-subsemilattice for lattices
> 2920f66a0e Trac #27798: Add `backend` option to associahedron and flow 
> polytope
> 98f3199887 Trac #27587: Follow up to #25680: Fix tempfile handling in doctests
> 0719be21c2 Trac #27473: Matrix inversion fails over a Laurent series ring
> 842a3dcd41 Trac #27444: Expose multithreaded fflas-ffpack features
> cee95e6b38 Trac #28404: Sign of hypergeometric motives is sometimes wrong
> af8bf5ead8 Trac #28400: fixing a few roles
> 1cdf4955c6 Trac #28398: _richcmp_ for quaternion algebra elements
> abb2397287 Trac #28397: fix some wrong doctests that were not run
> 2465a9e494 Trac #28396: faster Möbius matrix for Hasse diagrams
> 4b4b5bf81b Trac #28395: Bug in is_weil_polynomial
> 77466c5716 Trac #28393: add self-tests for polymake
> a7f0a353e5 Trac #28391: dependencies file for jupymake
> e7a3ec0d98 Trac #28377: polymake interface broken with "non-standard" 
> quadratic fields
> a535670711 Trac #28339: Random failure in src/sage/interfaces/expect.py
> f34f77e4da Trac #28271: Implement LexM traversal
> 304feb1626 Trac #28229: Generalized shifted prime tableau
> e570374675 Trac #27689: Implement is_pyramid, is_bipyramid, is_prism for 
> polytopes
> addde7bcc7 Trac #28380: bump up the version of givaro in spkg-configure.m4
> 8f1c30f031 Trac #28403: py3: crypto/block_cipher/present.py doctest failures
> 0ae7ffa669 Trac #25727: Prevent giac from giving localized output
> 109c1bd6c1 Trac #28060: Extensions of finite fields embeddings: we have 
> inverse image but `inverse_image` throws `NotImplemented`
> 0c5c45c0cf Trac #27937: Fix for functorial construction of monoid algebras
> fee35bf412 Trac #27851: Convert sqrt(D) to UCF
> 3b7ef2c62c Trac #27831: Small fix for is_symmetric for matrices 

Re: [sage-release] Sage 8.9.beta9 released

[E. Madison Bray]

Although it might be a little late, at this point, if we want to make
sure it's well-enough tested, I think we should try to include the
following in 8.9 final:

https://trac.sagemath.org/ticket/28356

As discussed when the first version of this code was added, it's
actually reasonably robust and might happen to fix other docbuild
hanging issues that have been reported (or at least the one we do know
the cause of; I don't know if there are other causes).  Everyone who's
tested this has built the docs successfully with it, and the code
itself is generally well-reviewed.

OTOH I can't promise there are *no* bugs--just not any I have found yet.

On Tue, Sep 3, 2019 at 1:22 AM 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
>
>
> bdf4b23d74 (trac/develop, tag: 8.9.beta9) Updated SageMath version to 
> 8.9.beta9
> c631202c12 Trac #28411: refresh the prompt in the installation guide
> 45482b13f0 Trac #28387: Implement function that returns the balanced digit 
> representation of an integer
> 4454ffec0d Trac #28384: py2: UnicodeDecodeError in doctest framework 
> exception handling
> 0c8192c3de Trac #28366: Lattice precision timing test fails on Windows 7 due 
> to low-ish clock resolution
> 5e1b351a89 Trac #28274: EnumeratedFamily should use integers as keys
> ec9715bb88 Trac #28172: Profile of a Finite Permutation Group
> dcf58df8b5 Trac #28154: SciPy: patch for missing coding lines in some source 
> files
> 82d75fd335 Trac #27917: Standardize doctest headers
> 04d5aab185 Trac #25817: RuntimeError: Encountered operator mismatch in 
> maxima-to-sr translation, integrate
> 45314bcbcf Trac #23639: Strange errors with roots() of polynomials over 
> polynomial rings
> f29cee985f Trac #28419: new pyflakes miscellanous cleanup
> 77bddf472a Trac #28417: removed deprecated stuff in integer_mod
> c565a3aa0a Trac #28412: upgrade Pynac to 0.7.26
> 2e47b34ab8 Trac #28408: fixing a few invalid escape sequences
> 877d26294b Trac #28407: py3: fix quantum_group_gap and graph_latex
> 3db8be3dc0 Trac #28399: remove deprecated things in integer.pyx
> 6a837c5ea6 Trac #27818: Meet-subsemilattice for lattices
> 2920f66a0e Trac #27798: Add `backend` option to associahedron and flow 
> polytope
> 98f3199887 Trac #27587: Follow up to #25680: Fix tempfile handling in doctests
> 0719be21c2 Trac #27473: Matrix inversion fails over a Laurent series ring
> 842a3dcd41 Trac #27444: Expose multithreaded fflas-ffpack features
> cee95e6b38 Trac #28404: Sign of hypergeometric motives is sometimes wrong
> af8bf5ead8 Trac #28400: fixing a few roles
> 1cdf4955c6 Trac #28398: _richcmp_ for quaternion algebra elements
> abb2397287 Trac #28397: fix some wrong doctests that were not run
> 2465a9e494 Trac #28396: faster Möbius matrix for Hasse diagrams
> 4b4b5bf81b Trac #28395: Bug in is_weil_polynomial
> 77466c5716 Trac #28393: add self-tests for polymake
> a7f0a353e5 Trac #28391: dependencies file for jupymake
> e7a3ec0d98 Trac #28377: polymake interface broken with "non-standard" 
> quadratic fields
> a535670711 Trac #28339: Random failure in src/sage/interfaces/expect.py
> f34f77e4da Trac #28271: Implement LexM traversal
> 304feb1626 Trac #28229: Generalized shifted prime tableau
> e570374675 Trac #27689: Implement is_pyramid, is_bipyramid, is_prism for 
> polytopes
> addde7bcc7 Trac #28380: bump up the version of givaro in spkg-configure.m4
> 8f1c30f031 Trac #28403: py3: crypto/block_cipher/present.py doctest failures
> 0ae7ffa669 Trac #25727: Prevent giac from giving localized output
> 109c1bd6c1 Trac #28060: Extensions of finite fields embeddings: we have 
> inverse image but `inverse_image` throws `NotImplemented`
> 0c5c45c0cf Trac #27937: Fix for functorial construction of monoid algebras
> fee35bf412 Trac #27851: Convert sqrt(D) to UCF
> 3b7ef2c62c Trac #27831: Small fix for is_symmetric for matrices over CDF
> 8f76f4d242 Trac #27760: Generalized Permutohedra and type H4 4-uniform 
> polytopes
> 67de66d92d Trac #27096: Bug in Buchberger algorithm over Tate algebra
> 6b8839d39f Trac #25823: maxima segfaults on integral computation
> 4583b4056e (tag: 8.9.beta8, trac/develop) Updated SageMath version to 
> 8.9.beta8
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/81faec30-03eb-4a66-b110-6417607004a7%40googlegroups.com.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [sage-release] Re: Sage 8.9.beta8 released

[E. Madison Bray]

IMO we should go forward with 8.9 for now and make the next version 9.0. By
then Python 3 support will be even more solid.


On Mon, Aug 26, 2019, 16:54 Frédéric Chapoton  wrote:

> The second file should have been fixed by
> https://trac.sagemath.org/ticket/28312
>
> but it was probably not tested..
>
> Le lundi 26 août 2019 16:14:13 UTC+2, Emmanuel Charpentier a écrit :
>>
>> On Debian testing running on core i7 + 16 GB RAM, ptest-python3 gets
>> three permanent failuresn already reported for the previous versions:
>>
>> --
>> sage -t --long --warn-long 161.7 src/sage/graphs/strongly_regular_db.pyx
>> # 4 doctests failed
>> sage -t --long --warn-long 161.7
>> src/sage/algebras/quantum_groups/quantum_group_gap.py  # 6 doctests failed
>> sage -t --long --warn-long 161.7
>> src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1 doctest failed
>> --
>>
>> Details on demand (seems identica (or very close)l to what's already been
>> reported, but I didn't formally check...).
>>
>> HTH,
>>
>>
>> Le lundi 26 août 2019 00:37:50 UTC+2, Volker Braun a écrit :
>>>
>>> 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
>>>
>>> It is nearing the end of the 8.9 merge window, so if you want something
>>> merged then this is your last chance.
>>>
>>> I'm inclined to name the next version 9.0. In particular, we now have
>>> Python 3 support that, while not perfect, is at least usable so we should
>>> mark that with a new major version. Also point-9 is a natural place to
>>> switch. If you want to voice your opinion on that issue: now is the time ;-)
>>>
>>>
>>> 4583b4056e (tag: 8.9.beta8, trac/develop) Updated SageMath version to
>>> 8.9.beta8
>>> 6565e63ee9 Trac #28373: new big bag of typos
>>> 0052843038 Trac #28297: Small optimizations to arithmetic in number
>>> fields of degree > 2
>>> a9f414a6f8 Trac #28057: Adding precision in computing the generators of
>>> the period lattice of an elliptic curve.
>>> 40c5efa0c8 Trac #28365: Use something instead of time() to ensure
>>> Manifold uniqueness in tests
>>> bd8504c9e8 Trac #28335: Cythonize Yen_k_shortest_simple_paths and
>>> feng_k_shortest_simple_paths
>>> c1d5763dc3 Trac #28147: Remove _derivative from Polynomial_template
>>> ef1517da96 Trac #28056: Sboxes Maintenance
>>> 05bd7671a2 Trac #26098: Implement L-functions using the PARI library
>>> c050128f4a Trac #20755: Bug in solve due to a bug in
>>> symbolic_expression_from_maxima_string
>>> 2a4bfffc48 Trac #28353: var() with single-element list/tuple crashes
>>> with unhandled TypeError
>>> 0a45dfc784 Trac #28371: py3: errors with optional package CSDP
>>> 5ab84a6fb3 Trac #28369: Improve progress report in gitlab-ci
>>> a8599952c3 Trac #28367: MR30: Update README.md: -py3 suffix
>>> 56f7684a57 Trac #28346: Use dots instead of precision in
>>> polynomial_element
>>> 8edd3f2797 Trac #28201: small cleanup of databases/cremona
>>> 1b7d07b6cc Trac #27573: PRESENT Block Cipher
>>> 5f22d242b6 Trac #28321: py3: rationals can not be initialized from a
>>> pair of big Python ints
>>> b972100c84 Trac #24494: Deprecate set_planar_positions()
>>> 42eb5103aa Trac #28364: MR29: Update faq-usage.rst
>>> 047992b031 Trac #28361: Implement parameter external_face of
>>> layout_planar()
>>> ae73a81a59 Trac #28343: Three.js: Support basic mesh plots
>>> 7e623eddb1 Trac #28116: Cython 0.29.12
>>> 7508513e65 Trac #28108: Py3: ValueError in graph_generators doctests
>>> with plantri optional package
>>> a98c0ab16f Trac #28347: Add as_integer_ratio() for Integer, Rational,
>>> RealNumber, RealDoubleElement
>>> 431187f776 Trac #28344: Fix some issues with submanifolds and improve
>>> their documentation
>>> 7c0d719021 Trac #28342: spkg-configure.m4 for m4ri, m4rie, givaro
>>> 5d6ac68f68 Trac #28228: Semistandard super tableau and standard super
>>> tableau for superRSK
>>> 7d561d89cf (tag: 8.9.beta7) Updated SageMath version to 8.9.beta7
>>>
>>> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/95fa41a9-4a1f-49fa-89d4-cfc931cb0792%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: [sage-release] Re: Sage 8.7.beta6 released

[E. Madison Bray]

On Thu, Aug 15, 2019 at 6:58 PM Markus Wageringel
 wrote:
>
> This also happened to me a few weeks ago. The underlying problem seems to be 
> that the uninstall script fails because it tries to call sage-dist-helpers, 
> but cannot find it. This file has recently been moved from src/bin to 
> build/bin, which the uninstall script cannot know about. Once upgraded to Gap 
> 4.10.2.p0, it points to the new location of sage-dist-helpers, so this 
> particular problem should not happen again.

Good catch!

> This has also been reported on devel [1,2] and might affect more Mac users 
> when upgrading to 8.9. Perhaps a copy of sage-dist-helpers could be added 
> back to src/bin for some deprecation period?

A symlink could do it.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34aGagRRR27DsBZ-7vYSYnpk5pX%3Dp%3DCWYPqO%3DuNhu%2B%3DkBg%40mail.gmail.com.

Re: [sage-release] Re: Sage 8.9.beta4 released

[E. Madison Bray]

On Tue, Aug 6, 2019 at 2:45 PM Eric Gourgoulhon  wrote:
>
> Le vendredi 2 août 2019 18:07:16 UTC+2, John H Palmieri a écrit :
>>
>>
>>
>> On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote:
>>>
>>>
>>>
>>> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit :

 Another question: does Flint pass its test suite on these machines?
>>>
>>>
>>> How could I run this test suite?
>>>
>>> Eric.
>>
>>
>> "sage -f -c flint"
>>
>
> Thanks for the tip.
> Being out of office, I ran the test suite on another computer (Core i7-6700HQ 
> + 16 GB RAM, running Ubuntu 18.04.2), which shows the same doctest failure 
> with Python3 Sage 8.9.beta5.
> The test suite seems passed, with many messages like
> [flint-2.5.2.p4] zz_pX_to_fmpz_mod_polyPASS
> [flint-2.5.2.p4] zz_pE_to_fqPASS
> [flint-2.5.2.p4] zz_pEX_to_fq_polyPASS
> (I did not see any "FAILED") and at the end:
> [flint-2.5.2.p4] Successfully installed flint-2.5.2.p4
> [flint-2.5.2.p4] Deleting temporary build directory
> [flint-2.5.2.p4] /home/eric/sage/py3/local/var/tmp/sage/build/flint-2.5.2.p4
> [flint-2.5.2.p4] Finished installing flint-2.5.2.p4.spkg
>
> Side note: the "./sage -f -c flint" command continued with
>
> New packages may have been installed.
> Re-running configure and make in case any dependent packages need updating.
>
> and then proceeded by installing
>
> arb-2.16.0.p0
> eclib-20190226
> linbox-1.6.3
> singular-4.1.1p2.p0
> pynac-0.7.24.p0
> sagelib-8.9.beta5
>
> Just in case, after "./sage -f -c flint", I run
> ./sage  -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx
> and get the same error:
>
> File "src/sage/rings/polynomial/polynomial_rational_flint.pyx", line 2055, in 
> sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
> Failed example:
> G = f.galois_group(); G
> Expected:
> Transitive group number 5 of degree 4
> Got:
> Exception (FLINT memory_manager). Unable to allocate memory.
> Transitive group number 5 of degree 4
>
> Again, on the very same computer, this doctest is passed with Python 2 Sage 
> 8.9.beta5.

It's possible this is similar to
https://trac.sagemath.org/ticket/28106 simply insofar as some test is
bumping up against the default 3300MB virtual memory limit imposed by
the test runner.

Which doesn't necessarily mean there isn't a problem: If some test is
using a lot more memory than it used to, such that it's bumping up
against that limit, there might be a leak or some other unintended
memory usage consequence to the way a test was written

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34ZObtAs0vFmSR8-qk63qRT4Xpq-Ku1KspHEohHA--%2BNtQ%40mail.gmail.com.

Re: [sage-release] Sage 8.8.rc1 released

[E. Madison Bray]

This ticket has also been languishing for no particular reason:
https://trac.sagemath.org/ticket/27724

It was previously looked upon favorably: It is a patch to GAP that has
already been accepted upstream by the GAP developers.  For a time it
was only held up for me to update the patch to the exact version
accepted upstream which I did a week ago.  By all rights it could have
been included in the first release candidate; just no one got around
to giving it a positive review explicitly.

I would have prodded people to do so immediately if I had known that a
"release candidate" would be created a day after but how could I have?

On Fri, Jun 14, 2019 at 4:14 PM Dima Pasechnik  wrote:
>
> Can we please get https://trac.sagemath.org/ticket/27950 in this release?
>
> It's docs on how to run Sage in conda, we are getting questions on it because
> our instructions are old, and cause at the moment conda needs a workaround.
>
> On Fri, Jun 14, 2019 at 7:40 AM 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
> >
> >
> > 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1
> > 8555a05c7d Trac #27467: weak order of permutations broken
> > 82e9b286db Trac #27883: AsymptoticRing: pass log-function more 
> > systematically
> > 2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0
> >
> > --
> > 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+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-release@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-release.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/CAAWYfq2S%3DkMgY3Bb7dLEE7Vp_3zt94XPYVbq22fL8BvW-03j%3DQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34aCeAKTQm_a_c_ZpWCck4nHJM9_Eeid%3DtHVSs64YJYWtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc1 released

[E. Madison Bray]

Perhaps we could try it anyways. Is there any concrete reason this is the
"end of a release cycle"?

It's not my fault if my ticket goes unreviewed for weeks and then suddenly
it's just seemingly arbitrarily the end of the release cycle that wasn't
communicated.

On Fri, Jun 14, 2019, 13:30 Volker Braun  wrote:

> I reviewed the ticket but rather not merge it at the last minute. Imho its
> quite possible that it breaks something on lesser-used platforms so we
> should merge it at the beginning of a release cycle, not the end.
>
>
> On Friday, June 14, 2019 at 10:59:37 AM UTC+2, E. Madison Bray wrote:
>>
>> Could somebody please review the following ticket:
>> https://trac.sagemath.org/ticket/27721
>>
>> It has been stalled for weeks now for no good reason other than, I
>> presume, lack of availability for someone to review it.
>>
>> I would really like this ticket to be resolved and merged before making
>> an 8.8 release because it's a regression that was introduced earlier in the
>> 8.8 development.
>>
>> On Fri, Jun 14, 2019, 08:40 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
>>>
>>>
>>> 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1
>>> 8555a05c7d Trac #27467: weak order of permutations broken
>>> 82e9b286db Trac #27883: AsymptoticRing: pass log-function more
>>> systematically
>>> 2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0
>>>
>>> --
>>> 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-r...@googlegroups.com.
>>> To post to this group, send email to sage-r...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/sage-release.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com
>>> <https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/63e45eb6-fb07-4fb9-b272-83d16d674862%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-release/63e45eb6-fb07-4fb9-b272-83d16d674862%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34a37Xf9%2B%2B%3D8bNg7htnRBY_GmnE17EeYRPWbikfYmUg5JA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc1 released

[E. Madison Bray]

(Accidentally sent before completing the message)

Could somebody please review the following ticket:
https://trac.sagemath.org/ticket/27721

It has been stalled for weeks now for no good reason other than, I presume,
lack of availability for someone to review it.

I would really like this ticket to be resolved and merged before making an
8.8 release because it's a regression that was introduced earlier in the
8.8 development.

I don't think we should be making a release with a known regression that
IMO has a perfectly good fix that has only not been merged due to lacking a
final sign-off by someone. I marked the issue as "critical" and not
"blocker" only because I can technically work around it, but shouldn't have
to.

Unless there's a serious reason to rush this release please resolve this
issue first.

On Fri, Jun 14, 2019, 10:59 E. Madison Bray  wrote:

> Could somebody please review the following ticket:
> https://trac.sagemath.org/ticket/27721
>
> It has been stalled for weeks now for no good reason other than, I
> presume, lack of availability for someone to review it.
>
> I would really like this ticket to be resolved and merged before making an
> 8.8 release because it's a regression that was introduced earlier in the
> 8.8 development.
>
> On Fri, Jun 14, 2019, 08:40 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
>>
>>
>> 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1
>> 8555a05c7d Trac #27467: weak order of permutations broken
>> 82e9b286db Trac #27883: AsymptoticRing: pass log-function more
>> systematically
>> 2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-release@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-release.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com
>> <https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34bDdSmDEXfDhi7WaFUMVKv50GGZKCfHGYp_J9eJWF7NrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc1 released

[E. Madison Bray]

Could somebody please review the following ticket:
https://trac.sagemath.org/ticket/27721

It has been stalled for weeks now for no good reason other than, I presume,
lack of availability for someone to review it.

I would really like this ticket to be resolved and merged before making an
8.8 release because it's a regression that was introduced earlier in the
8.8 development.

On Fri, Jun 14, 2019, 08:40 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
>
>
> 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1
> 8555a05c7d Trac #27467: weak order of permutations broken
> 82e9b286db Trac #27883: AsymptoticRing: pass log-function more
> systematically
> 2393acebc3 (tag: 8.8.rc0) Updated SageMath version to 8.8.rc0
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/232e2bcd-22aa-4013-9801-d451b7c124f5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34b42oUtX6XAbuP-TPhuXrnm0_OvbWZ9AG54cUSF237rKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.rc0 released

[E. Madison Bray]

On Wed, Jun 12, 2019 at 3:14 PM Dima Pasechnik  wrote:
>
> On Wed, Jun 12, 2019 at 2:03 PM E. Madison Bray  wrote:
> >
> > On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik  wrote:
> > >
> > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray  
> > > wrote:
> > > >
> > > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik  
> > > > wrote:
> > > > >
> > > > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray 
> > > > >  wrote:
> > > > > >
> > > > > > I don't know why the rush to call this a release candidate when 
> > > > > > there are clearly still several outstanding problems to be resolved 
> > > > > > before the next release.
> > > > > >
> > > > > > As usual absolutely zero communication of a plan or coordination 
> > > > > > with the community.
> > > > > >
> > > > > my ongoing complaint is the lack of progress on the improving the
> > > > > release procedures to make it easy to change the configure package.
> > > > > At the moment it is extremely sub-optimal, with endless merge
> > > > > conflicts resulting solely from the need to have the ticket branch
> > > > > that changes configure.ac, spkg-configure.m4 files, and its friends,
> > > > > such as sage/big/sage-env* things coming with its configure "package"
> > > > > tarball. This leaves tickets of this sort languishing for months, as
> > > > > it's not really possible to get them in sync with the ongoing release
> > > > > process (already due to configure tarballs coming with artificial
> > > > > version numbers, that should not clash etc).
> > > > >
> > > > > I continue to think that the release process should not require
> > > > > updates of configure package. Sage seems to unique in its insistence
> > > > > on the release process depending on the autogenerated dumps...
> > > >
> > > > One very easily solution to this, and I know some people will shudder
> > > > (myself included) is to simply include the configure script in the
> > > > repository.  Yes, it's generated.  But there's precedent for this.
> > >
> > > well, it would make running patchbots easier, but
> > > I don't see how this would help the release management,
> > > as auto-merging would be still be out of the question.
> > >
> > > The auto-generated crud is simply unmergable, by and large.
> >
> > That really depends on the change in question. Oftentimes they're
> > quite discrete.  It only becomes a mess when you have to do lots of
> > AC_REQUIREs and thus things get reordered in the configure script.
> >
> > That is a problem for us right now since we're doing a lot of
> > heavy-lifting on configure.  Once a lot of that is out of the way it
> > will calm down a bit.
>
> given the speed things at present move on #27330, it can easily take a
> year or two.
> And still, as we shift more into using external libraries, there is
> going to be more tweaking of
> the configure package than in the olden days...

Absolutely; which is maybe a good reason to just include the configure
script in the repository.  True, that would not fix all the merge
issues you're struggling with, but on some level that is almost
unavoidable, at least when testing/building on systems that are not
able to run autoconf smoothly.  A more complex workaround involving a
separate build system just for autoconf is probably not worth the
effort compared to that one minor concession.

Meanwhile, keeping it in the repository will make it much easier to
maintain said "tweaks".

I'm not going to fight tooth-and-nail for it, but I'll just emphasize

1) We'd be far from the first project to make this concession
2) It will make enough peoples' lives easier that it's not so bad to
have one generated (plain text) file in the repo


> > For the most part, when making small tweaks to
> > a single autoconf macro, the resulting change in the generated
> > configure script is more-or-less a direct translation.
> >
> > So for fixing bugs in configure alone it would be useful to keep the
> > generated script in the repository and not have to mess with this
> > configure tarball every time.
> >
> > --
> > 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

Re: [sage-release] Re: Sage 8.8.rc0 released

[E. Madison Bray]

On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik  wrote:
>
> On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray  wrote:
> >
> > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik  wrote:
> > >
> > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray  
> > > wrote:
> > > >
> > > > I don't know why the rush to call this a release candidate when there 
> > > > are clearly still several outstanding problems to be resolved before 
> > > > the next release.
> > > >
> > > > As usual absolutely zero communication of a plan or coordination with 
> > > > the community.
> > > >
> > > my ongoing complaint is the lack of progress on the improving the
> > > release procedures to make it easy to change the configure package.
> > > At the moment it is extremely sub-optimal, with endless merge
> > > conflicts resulting solely from the need to have the ticket branch
> > > that changes configure.ac, spkg-configure.m4 files, and its friends,
> > > such as sage/big/sage-env* things coming with its configure "package"
> > > tarball. This leaves tickets of this sort languishing for months, as
> > > it's not really possible to get them in sync with the ongoing release
> > > process (already due to configure tarballs coming with artificial
> > > version numbers, that should not clash etc).
> > >
> > > I continue to think that the release process should not require
> > > updates of configure package. Sage seems to unique in its insistence
> > > on the release process depending on the autogenerated dumps...
> >
> > One very easily solution to this, and I know some people will shudder
> > (myself included) is to simply include the configure script in the
> > repository.  Yes, it's generated.  But there's precedent for this.
>
> well, it would make running patchbots easier, but
> I don't see how this would help the release management,
> as auto-merging would be still be out of the question.
>
> The auto-generated crud is simply unmergable, by and large.

That really depends on the change in question. Oftentimes they're
quite discrete.  It only becomes a mess when you have to do lots of
AC_REQUIREs and thus things get reordered in the configure script.

That is a problem for us right now since we're doing a lot of
heavy-lifting on configure.  Once a lot of that is out of the way it
will calm down a bit.  For the most part, when making small tweaks to
a single autoconf macro, the resulting change in the generated
configure script is more-or-less a direct translation.

So for fixing bugs in configure alone it would be useful to keep the
generated script in the repository and not have to mess with this
configure tarball every time.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34b3SLks2hmA_RmF24ikyW3Z9JR-gi3LtnjuAnBurwfecQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.rc0 released

[E. Madison Bray]

On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik  wrote:
>
> On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray  wrote:
> >
> > I don't know why the rush to call this a release candidate when there are 
> > clearly still several outstanding problems to be resolved before the next 
> > release.
> >
> > As usual absolutely zero communication of a plan or coordination with the 
> > community.
> >
> my ongoing complaint is the lack of progress on the improving the
> release procedures to make it easy to change the configure package.
> At the moment it is extremely sub-optimal, with endless merge
> conflicts resulting solely from the need to have the ticket branch
> that changes configure.ac, spkg-configure.m4 files, and its friends,
> such as sage/big/sage-env* things coming with its configure "package"
> tarball. This leaves tickets of this sort languishing for months, as
> it's not really possible to get them in sync with the ongoing release
> process (already due to configure tarballs coming with artificial
> version numbers, that should not clash etc).
>
> I continue to think that the release process should not require
> updates of configure package. Sage seems to unique in its insistence
> on the release process depending on the autogenerated dumps...

One very easily solution to this, and I know some people will shudder
(myself included) is to simply include the configure script in the
repository.  Yes, it's generated.  But there's precedent for this.
Among other projects, CPython includes their configure script in the
repository.  This allows developers to get right up-and-running with
./configure without having to fuss with the nuances of different
versions of autotools on different systems.  Only developers actually
working on configure issues need to worry about that.  It's quite
convenient.


> > On Tue, Jun 11, 2019, 02:28 Kwankyu Lee  wrote:
> >>
> >>
> >>
> >> On Monday, June 10, 2019 at 4:40:52 PM UTC+9, Sébastien Labbé wrote:
> >>>
> >>> Testing the following optional and external packages:
> >>>
> >>> External software detected for doctesting: 
> >>> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc
> >>>
> >>> Using 
> >>> --optional=4ti2,bliss,cbc,ccache,cmake,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,mpir,ninja_build,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,qhull,rst2ipynb,sage,topcom
> >>> External software to be detected: 
> >>> cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,macaulay2,magma,maple,mathematica,matlab,octave,pandoc,scilab
> >>>
> >>> I get:
> >>>
> >>> --
> >>> sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
> >>> sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed
> >>> --
> >>>
> >>> and only the following is reproducible:
> >>>
> >>> --
> >>> sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
> >>> --
> >>>
> >>> Follow up at https://trac.sagemath.org/ticket/25536
> >>
> >>
> >> I see Sage has been much improved in this respect. Thank you for your 
> >> persistent efforts!
> >>
> >> --
> >> 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+unsubscr...@googlegroups.com.
> >> To post to this group, send email to sage-release@googlegroups.com.
> >> Visit this group at https://groups.google.com/group/sage-release.
> >> To view this discussion on the web visit 
> >> https://groups.google.com/d/msgid/sage-release/35dc58d0-763e-4da4-b1c4-e8f981665b49%40googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > 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+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-release@googlegroups.com.
> > Visit this group at https:/

Re: [sage-release] Re: Sage 8.8.rc0 released

[E. Madison Bray]

I don't know why the rush to call this a release candidate when there are
clearly still several outstanding problems to be resolved before the next
release.

As usual absolutely zero communication of a plan or coordination with the
community.

On Tue, Jun 11, 2019, 02:28 Kwankyu Lee  wrote:

>
>
> On Monday, June 10, 2019 at 4:40:52 PM UTC+9, Sébastien Labbé wrote:
>>
>> Testing the following optional and external packages:
>>
>> External software detected for doctesting:
>> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc
>>
>> Using
>> --optional=4ti2,bliss,cbc,ccache,cmake,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,mpir,ninja_build,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,qhull,rst2ipynb,sage,topcom
>> External software to be detected:
>> cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,macaulay2,magma,maple,mathematica,matlab,octave,pandoc,scilab
>>
>> I get:
>>
>> --
>> sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
>> sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed
>> --
>>
>> and only the following is reproducible:
>>
>> --
>> sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
>> --
>>
>> Follow up at https://trac.sagemath.org/ticket/25536
>>
>
> I see Sage has been much improved in this respect. Thank you for your
> persistent efforts!
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/35dc58d0-763e-4da4-b1c4-e8f981665b49%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34bCgqGe6UCE2eoDVq%2Bmg%2BW8f3nnRrBKztutSLvT%2BjicdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.beta6 released

[E. Madison Bray]

The tests should make sure nothing in ~/.gap is ever loaded if at all
possible (e.g. update the GAP interfaces to add an option to disable use of
~/.gap` when running the tests, for example)

On Sat, May 25, 2019, 03:22 François Bissey  wrote:

> We’ll want some kind of follow up. The test will fail if you have
> something in ~/.gap.
> Not just on sage-on-gentoo.
> The question is whether the pexpect interface should continue starting
> `gap` with the
> “-r” option or not.
>
> François
>
> > On 25/05/2019, at 12:17 PM, Steven Trogdon 
> wrote:
> >
> > Found this also first on s-o-g. So should ~/.gap be empty or is a
> follow-up to https://trac.sagemath.org/ticket/27681 necessary?
> > On Friday, May 24, 2019 at 7:04:53 PM UTC-5, François Bissey wrote:
> > You have something in ~/.gap. See
> https://trac.sagemath.org/ticket/27681#comment:30
> >
> > > On 25/05/2019, at 12:02 PM, Steven Trogdon 
> wrote:
> > >
> > > As far as I know this failure started with this beta.
> > >
> > > sage -t --long src/sage/tests/gap_packages.py
> > > **
> > > File "src/sage/tests/gap_packages.py", line 137, in
> sage.tests.gap_packages.all_installed_packages
> > > Failed example:
> > > all_installed_packages() == all_installed_packages(gap=gap)
> > > Expected:
> > > True
> > > Got:
> > > False
> > > **
> > > 1 item had failures:
> > >1 of   4 in sage.tests.gap_packages.all_installed_packages
> > > [10 tests, 1 failure, 1.04 s]
> > >
> > >
> > > For info:
> > >
> > > sage: from sage.tests.gap_packages import all_installed_packages
> > > sage: all_installed_packages()
> > > ('AtlasRep',
> > >  'FactInt',
> > >  'GAPDoc',
> > >  'SmallGrp',
> > >  'alnuth',
> > >  'atlasrep',
> > >  'autpgrp',
> > >  'crisp',
> > >  'ctbllib',
> > >  'fga',
> > >  'irredsol',
> > >  'laguna',
> > >  'polenta',
> > >  'polycyclic',
> > >  'primgrp',
> > >  'resclasses',
> > >  'sophus',
> > >  'tomlib',
> > >  'transgrp')
> > > sage: all_installed_packages(gap=gap)
> > > ('FactInt',
> > >  'GAPDoc',
> > >  'SmallGrp',
> > >  'alnuth',
> > >  'atlasrep',
> > >  'autpgrp',
> > >  'crisp',
> > >  'ctbllib',
> > >  'fga',
> > >  'irredsol',
> > >  'laguna',
> > >  'polenta',
> > >  'polycyclic',
> > >  'primgrp',
> > >  'resclasses',
> > >  'sophus',
> > >  'tomlib',
> > >  'transgrp')
> > >
> > > ls ~/.gap/pkg/
> > > AtlasRep
> > >
> > >
> > >
> > > --
> > > 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-r...@googlegroups.com.
> > > To post to this group, send email to sage-r...@googlegroups.com.
> > > Visit this group at https://groups.google.com/group/sage-release.
> > > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/1969b326-0280-430f-8e84-45053acf1b05%40googlegroups.com.
>
> > > For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > 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+unsubscr...@googlegroups.com.
> > To post to this group, send email to sage-release@googlegroups.com.
> > Visit this group at https://groups.google.com/group/sage-release.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/f8f00f9a-44cf-4a73-8ec1-fd25ccbcd536%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/B31F9E94-A1D6-4EFC-A15A-9065C666B7AC%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34bYbXOngnCO2%3DP_foQEg5xRn_BeFg8x66mrPh7A4YwcPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.beta5 released

[E. Madison Bray]

On Sat, May 11, 2019 at 3:40 PM 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
>
> baff1c42dd (tag: 8.8.beta5) Updated SageMath version to 8.8.beta5
> 71ded1d112 Trac #27797: remove one old note, and pep cleanup of 
> zariski_vankampen
> 2735ee2c04 Trac #27786: yet another harvest of typos
> bd56d9 Trac #27796: get rid of dollar signs in elliptic curves
> 52fdfad1d7 Trac #27795: spkg-configure.m4 for perl_term_readline_gnu
> 595929f120 Trac #27794: py3: doctests in sets
> 8fa7e9c235 Trac #27782: 1 pynormaliz doctest failing in 
> src/sage/geometry/polyhedron/backend_normaliz.py
> ddbf8517cd Trac #27779: Py3: Fix dynamics.arithmetic_dynamics for python3
> 3f3f9f8fc6 Trac #27776: some py3 fixes in ext
> 41b531ebb0 Trac #27755: some fixes and pep cleanup in number fields orders
> 51b11e4f33 Trac #27680: MR11: Lazy initialization of libgap
> 28b02c41ef Trac #27642: Re-run configure+make after installing an SPKG with 
> sage -i
> 2512f066d4 Trac #27284: spkg-configure.m4 for pcre
> 11ce0d345d Trac #24905: Upgrade polymake to version 3.4
> 320848ca5d Trac #2693: Sage should have generic resultant implementation for 
> multivariate polynomials
> dde47f6924 Trac #27771: py3: matroid/unpickling.pyx fix
> b7f85e720c Trac #27768: py3: fix a flaky doctest in multipoly element
> adc54ac6cb Trac #27767: py3: fix regression in qqbar.py
> 027201ea48 Trac #27766: Add a few more 'optional - build' tags
> 080beb1a9c Trac #27748: avoid using is_package_installed in generic_graph.py
> 2cc376afb3 Trac #27711: Remove deprecated parameter "implementation" from 
> Graph and DiGraph constructors
> 2a23b96573 Trac #27706: building doc: u'\xe9' in position 19: ordinal not in 
> range(128)
> 7073b50509 Trac #27559: py3: maxint to maxsize in cryptominisat interface
> b26d1ad7f4 Trac #26982: remove dynamics/interval_exchanges and 
> dynamics/flat_surfaces
> b38af08e41 Trac #24082: Genus from a TorsionQuadraticModules and a signature 
> pair
> ba0f482123 Trac #27236: PariError: bug in gerepile when factoring polynomials
> 2264f560b8 Trac #27756: pyflakes and pep cleanup for free monoids
> 55699b1a57 Trac #27743: Hyperplane Arrangement enhancements
> 9cd0936c52 Trac #27739: commutative rings have commutative monoids of ideals
> b5ebee39f2 Trac #27622: Minor import fix in misc/package.py
> c63bda62ab Trac #27759: cleanup pyflakes warnings in sage.rings.asymptotic
> b317ba9555 Trac #27758: py3: remaining fixes in doc/en
> e57105d5a2 Trac #27757: py3: remaining fixes in categories
> b4f31996cd Trac #27746: Upgrade LiDIA to v2.3.0+latte-patches-2019-05-01
> c78e8ce544 Trac #27742: PolymakeElement._sage_: Handle polymake type 
> Polyhedron
> c1b8bd1bcf Trac #27741: bug in sympy conversion of hypergeometric with tuple 
> arg of length 1
> 4fb11501c4 Trac #27740: pyflakes and pep8 cleanup in features
> b607472081 Trac #27735: Support matrix input in @interact
> 5dbc7ced54 Trac #27732: py3: fix one doctest in semigroups category
> 76b3fb388f Trac #27674: py3: some fixes to rings/polynomial
> 3b73058655 Trac #27653: Update sympy to 1.4
> 1363b54194 Trac #27641: SAGE_SPKG_CONFIGURE macro: Add new pre-check and 
> post-check optional arguments
> 9c129a313c Trac #27588: Py3: Fix libs.ntl.ntl_ZZ_pX.pyx doctests.
> 027d0c5e6c Trac #27487: spkg-configure.m4 for cmake
> cba1d16698 Trac #27479: Univariate PolynomialRing with 'negdegrevlex' order 
> does not get 'ds' order in Singular
> d8c5874b48 Trac #27262: remove "Replacing library search directory in linker 
> " in src/setup.py
> 86c5bb0002 Trac #26718: Upgrade to three.js r100
> 46912716a3 Trac #26592: py3: combinat/designs: bytes-like object is required, 
> not 'str'
> 40f87c92b6 Trac #25989: PolynomialSequence should handle iterator as input
> 37c2490525 Trac #27753: Fix patchbot on Python 3
> 5c0b498fb2 Trac #27656: py3: Fix table display in Jupyter notebook with Sage 
> kernel
> b9782553cc Trac #27751: barvinok spkg-install syntax error
> d765ee2917 (tag: 8.8.beta4) Updated SageMath version to 8.8.beta4

make ptestlong passes on Cygwin 64 *with* the fixes from the following
tickets merged in as well:

https://trac.sagemath.org/ticket/27721
https://trac.sagemath.org/ticket/27724
https://trac.sagemath.org/ticket/27514

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/CAOTD34YN5s6_ww_zJzjSUL4YndjA1y5h3EOo55pQYeTXg72gxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.7.rc0 released

[E. Madison Bray]

Could someone have a look at, and maybe give positive-review to
https://trac.sagemath.org/ticket/27385.  It would be lovely if we
could get this fix in 8.7, and the patch I added only affects Cygwin.
Bernard Parisse has said he will fix the issue upstream but I haven't
followed through yet on whether that's been done.

It's a fairly random bug, but it does have potential to cause pain for users.

As an aside, I'm surprised to find that sage.interfaces.giac is still
used at all in Sage (particularly in sage.calculus) instead of using
sage.libs.giac.  But it seems giacpy_sage is still an optional
package.  What are the chances of moving forward on making that
standard functionality, and deprecating/dropping the pexpect interface
(a move I'd like to make in as many cases as possible...)

On Wed, Mar 20, 2019 at 12:03 AM 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
>
>
> 2a9c447e04 (tag: 8.7.rc0, trac/develop) Updated SageMath version to 8.7.rc0
> f2a89574b1 Trac #27214: libgap memory allocation on Cygwin
> 593f669d66 Trac #27490: Simplistic multiprocessing.Pool replacement for 
> parallel docbuild on older Cygwin
> b5437289a5 Trac #27489: *** SIG 14 *** outside sig_on
> b1a58d9670 Trac #27461: Minor test failure on Cygwin in 
> ComplexDoubleElement._pow_
> a6041ad3e8 Trac #27421: .coefficient of multi-variate polynomial should 
> accept output of .exponents()
> eb8d110a06 Trac #27485: Use sdh_cmake for configuring primecount
> 1cfb97ac95 Trac #27484: Add sdh_cmake helper
> 56d6b08c80 Trac #27476: Add patch to zn_poly for support for Python 2.6
> cca8152c2f Trac #27474: some care for BAD references in finite_word.py
> 02461b6b07 Trac #27440: py3: fixing the hash of real and complex lazy fields
> d0b17b1c6f Trac #27418: Global function fields: completions
> 5f48119306 Trac #27463: Sage cannot open a Jupyter notebook directly
> 4b93d20a42 Trac #27070: Upgrade to Cysignals 1.10.2
> c26f30d8fa Trac #27471: py3:fix last doctest in affine_curve.py
> 5fab23be51 Trac #27470: MR10: Update trac.rst
> ec80f14992 Trac #27466: py3: modules/with_basis/morphism.py
> ff54389b61 Trac #27432: py3: fix last doctest in ell_rational_field
> 492be643fb Trac #27374: make_any_gap_element() should not be called inside 
> sig_on(), part 2
> c28b99ccab Trac #24101: Implement Katz centrality and related methods for 
> graphs
> a8a19809f6 Trac #24094: Effective Resistance for Graphs
> ae38e0e0c8 Trac #23052: operations between sage and gmpy2 numbers
> a343db4f1c Trac #22574: Add .change_ring() method for polyhedra
> 1432f483a6 Trac #9707: Add a "signless" option to laplacian
> 6edd9ad92c Trac #27215: Remove broken SAGE_BUILD_TOOLCHAIN support
> b6455b8dcc Trac #27458: some cleanup in elliptic curves
> 1e2dc5b15b Trac #27436: Update Link to PRESENT paper
> ab8ee51c4b Trac #27455: remove the deprecated file dict_addition
> acbf6b4396 Trac #27430: more choices of algorithms for Coxeter Smith form of 
> posets
> e5f1759a36 Trac #27283: documentation for ModularSymbols says that only 
> weight 2 is supported, but any weight at least 2 is supported
> db49315d16 Trac #27460: fix issue in graph_plot_js
> f149a665e0 Trac #27459: py3: fix again doctests in matrix groups
> 27327cba7b Trac #27456: py3: fix one file in sets/
> f8944c1684 Trac #27454: py3: partial fix for crypto/lwe
> 4e1a6a2e44 Trac #27453: py3: fix last doctest in soliton.py
> f6d2c6a3c4 Trac #27452: py3: fundamental group of simplicial complexes
> 024c0d4b4f Trac #27451: speedup of induced trivial character basis
> f570e3a7fc Trac #27360: upgrade eclib to v20190226
> bc7c117e21 Trac #27346: py3: fix FindStat interface and FancyTuple
> a49f71755b Trac #27359: Test for sage_makedirs breaks Sage on Windows
> 9c2af6989e Trac #27439: Py3: Fix bounded_integer_sequences.pyx for python3.
> 76b7b821ac Trac #27443: spring cleanup for QQbar
> 73d5bfd712 Trac #27135: pep8 in digraph_generators.py (part 2)
> 7bc1a37192 Trac #27449: py3: fix all doctests in schemes/product_projective
> 54cd3d6430 Trac #27441: Add more trig functions to complex_arb and real_arb
> 5d5f495eb5 Trac #27427: Don't use bare except: statements
> ea852a4ea0 Trac #14999: subgraph_search does not like labeled edges
> d982527e6a Trac #27438: Properly re-enable USE_TLS=1 when building OpenBLAS 
> SPKG
> 10407524b1 (tag: 8.7.beta7) Updated SageMath version to 8.7.beta7
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the 

Re: [sage-release] Sage 8.7.rc0 released

[E. Madison Bray]

Thank Volker,

On my Ubuntu machine,

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

I got one seemingly random failure I haven't seen before:

sage -t --long 
src/sage/tests/books/computational-mathematics-with-sagemath/graphique_doctest.py
**
File 
"src/sage/tests/books/computational-mathematics-with-sagemath/graphique_doctest.py",
line 112, in 
sage.tests.books.computational-mathematics-with-sagemath.graphique_doctest
Failed example:
for i in srange(-2, 2, 0.2):  # long time
g += line(desolve_rk4(DE, y(x), ics=[1, i],\
  step=0.05, end_points=[0,2]))
g += line(desolve_rk4(DE, y(x), ics=[-1, i],\
  step=0.05, end_points=[-2,0]))
Exception raised:
Traceback (most recent call last):
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 671, in _run
self.compile_and_execute(example, compiler, test.globs)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 1095, in compile_and_execute
exec(compiled, globs)
  File "",
line 3, in 
step=RealNumber('0.05'), end_points=[Integer(0),Integer(2)]))
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/calculus/desolvers.py",
line 1378, in desolve_rk4
sol_2=maxima(cmd).sage()
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/interfaces/interface.py",
line 1074, in sage
return self._sage_(*args, **kwds)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/interfaces/maxima_abstract.py",
line 1238, in _sage_
maxima=self.parent())
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/calculus/calculus.py",
line 2210, in symbolic_expression_from_maxima_string
raise TypeError("unable to make sense of Maxima expression
'%s' in Sage"%s)
TypeError: unable to make sense of Maxima expression
'(kill(sage4)$o44)[[1.0,-2.0],[1.05,-2.149874965475482],[1.1,-2.29839830521],[1.15,-2.446624921487998],[1.2,-2.59109207452],[1.25,-2.7343749020044],[1.3,-2.872999899091065],[1.35,-3.007124899832311],[1.4,-3.13503712506],[1.45,-3.258874910310362],[1.5,-3.37419279643],[1.55,-3.483624930334245],[1.6,-3.5834323656],[1.65,-3.675374957788335],[1.7,-3.75673823437],[1.75,-3.828124991202094],[1.8,-3.88809806273],[1.85,-3.935875029535953],[1.9,-3.97150306113],[1.95,-3.992625072044261],[2.0,-4.00094688424]]'
in Sage
**
1 item had failures:
   1 of 117 in 
sage.tests.books.computational-mathematics-with-sagemath.graphique_doctest
[116 tests, 1 failure, 56.94 s]


It passed when run again individually, so I am not too worried about
it.  Just posting here in case anyone has any ideas.

On Wed, Mar 20, 2019 at 12:03 AM 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
>
>
> 2a9c447e04 (tag: 8.7.rc0, trac/develop) Updated SageMath version to 8.7.rc0
> f2a89574b1 Trac #27214: libgap memory allocation on Cygwin
> 593f669d66 Trac #27490: Simplistic multiprocessing.Pool replacement for 
> parallel docbuild on older Cygwin
> b5437289a5 Trac #27489: *** SIG 14 *** outside sig_on
> b1a58d9670 Trac #27461: Minor test failure on Cygwin in 
> ComplexDoubleElement._pow_
> a6041ad3e8 Trac #27421: .coefficient of multi-variate polynomial should 
> accept output of .exponents()
> eb8d110a06 Trac #27485: Use sdh_cmake for configuring primecount
> 1cfb97ac95 Trac #27484: Add sdh_cmake helper
> 56d6b08c80 Trac #27476: Add patch to zn_poly for support for Python 2.6
> cca8152c2f Trac #27474: some care for BAD references in finite_word.py
> 02461b6b07 Trac #27440: py3: fixing the hash of real and complex lazy fields
> d0b17b1c6f Trac #27418: Global function fields: completions
> 5f48119306 Trac #27463: Sage cannot open a Jupyter notebook directly
> 4b93d20a42 Trac #27070: Upgrade to Cysignals 1.10.2
> c26f30d8fa Trac #27471: py3:fix last doctest in affine_curve.py
> 5fab23be51 Trac #27470: MR10: Update trac.rst
> ec80f14992 Trac #27466: py3: modules/with_basis/morphism.py
> ff54389b61 Trac #27432: py3: fix last doctest in ell_rational_field
> 492be643fb Trac #27374: make_any_gap_element() should not be called inside 
> sig_on(), part 2
> c28b99ccab Trac #24101: Implement Katz centrality and related methods for 
> graphs
> a8a19809f6 Trac #24094: Effective Resistance for Graphs
> ae38e0e0c8 Trac #23052: operations between sage and gmpy2 numbers
> a343db4f1c Trac #22574: Add .change_ring() method for polyhedra
> 1432f483a6 Trac #9707: Add a "signless" 

Re: [sage-release] Sage 8.7.beta7 released

[E. Madison Bray]

On Sun, Mar 10, 2019 at 10:01 AM 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
>

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

Had one strange failure with this build.  Admittedly I was running the
tests with -p 12:

sage -t --long src/sage/libs/flint/nmod_poly_linkage.pxi  # Timed out
(and interrupt failed)

It hanged, and ultimately timed out, at

sage: n = 2^23 ## line 518 ##
sage: alarm(0.2); x^n; cancel_alarm() ## line 519 ##

/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/cysignals/signals.so(+0x82d5)[0x2b9383b742d5]
/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/cysignals/signals.so(+0x837f)[0x2b9383b7437f]
/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/cysignals/signals.so(+0xa6ff)[0x2b9383b766ff]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x2b937b8ed330]
/lib/x86_64-linux-gnu/libc.so.6(+0x10bd2b)[0x2b937bc06d2b]
/lib/x86_64-linux-gnu/libc.so.6(+0x850da)[0x2b937bb800da]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x55)[0x2b937bb7dad5]
/home/embray/src/sagemath/sage/local/lib/libpython2.7.so.1.0(+0x8d4dc)[0x2b937b5454dc]
/home/embray/src/sagemath/sage/local/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x81b7)[0x2b937b5c7107]

So that's strange.

Running that one test again by itself and it passed immmediately in
under a second:

sage -t --long src/sage/libs/flint/nmod_poly_linkage.pxi
[183 tests, 0.37 s]

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.7.beta7 released

[E. Madison Bray]

On Sun, Mar 10, 2019 at 12:08 PM Emmanuel Charpentier
 wrote:
>
> On Debian testing running on core i7 + 16 GB RAM, ptestlong gets one 
> transient failure :
>
> --
> sage -t --long --warn-long 146.8 src/sage/rings/number_field/number_field.py  
> # 1 doctest failed
> --
>
> which passes when ran standalone. The failure recorded in tkhe log file is :
>
> Failed example:
> for chi in G:
> D = ModularSymbols(chi, 2, 
> -1).cuspidal_subspace().new_subspace().decomposition()
> for f in D:
> elt = f.q_eigenform(10, 'alpha')[3]
> assert elt.is_integral()
> Exception raised:
> [ ... ]
> SystemError: calling remove_from_pari_stack() inside sig_on()

I have seen this as well: https://trac.sagemath.org/ticket/27374#comment:4



> Le dimanche 10 mars 2019 10:01:25 UTC+1, Volker Braun a écrit :
>>
>> 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
>>
>>
>> 10407524b1 (tag: 8.7.beta7, trac/develop) Updated SageMath version to 
>> 8.7.beta7
>> 695a8e0aea Trac #27400: minor details in mac-app
>> fe0269a91b Trac #27433: py3: fix last doctest in mutable_poset
>> 769697af01 Trac #27431: py3: fix misc/unittest
>> 3aa99d3439 Trac #27216: Fix spkg-legacy-uninstall for GAP
>> 5724e3ba92 Trac #25035: Use sage-dist-helpers + add DESTDIR support for 
>> flint and arb
>> 0de0fbbddd Trac #27399: Expected ValueError when calling set_vertex()
>> f708233005 Trac #27423: fix constructor of ConvexRationalPolyhedralCone
>> 21f64546a0 Trac #27370: Global function fields: differentials
>> 4e89a1e0dc Trac #27291: Frenchism (typos): "representative" should be used 
>> instead of  "representant"
>> 4e247fddc7 Trac #27389: Fix src/build/cythonized/build/cythonized directory
>> 063963fdef Trac #27429: some little code cleanup
>> 5b5d06ae9e Trac #27398: using sdh dist helpers for plantri
>> 80baa84ed6 Trac #27386: Cache gens_dict()
>> 9f275f1612 Trac #27426: update openssl
>> 8a8be1a91a Trac #27420: cypari2 version 2.1.0
>> f85d8ebb9b Trac #27411: add monoid of knots
>> 0c830408e8 Trac #24741: py3: numerous additional fixes for sage.numerical
>> ac9a885ca4 Trac #27414: Fix some py3 doctests in algebras
>> 8fcc6fbf4c Trac #27417: Fix Cython vtable warnings in 
>> padic_generic_element.pyx
>> 820b5dccec Trac #27416: Makefile buildbot-python3 target should build the 
>> documentation
>> 569c11c2aa Trac #27415: py3: algebras/lie_algebras
>> 25b2a080a4 Trac #27410: simplify and speedup of 
>> YoungsLatticePrincipalOrderIdeal
>> 7ad8037267 Trac #27407: remove deprecated stuff in designs
>> 839360d9ee Trac #27402: remove the doctest flag "optional - gmpy2"
>> 2ee44db2d1 Trac #27387: bug in saturation of points on elliptic curves over 
>> number fields
>> c92ab53112 Trac #27409: removed deprecated method in manifolds
>> 4c86724bcd Trac #27406: py3: various fixes about print and hash
>> 880ed5f5d7 Trac #27405: Ignore pip stderr when querying packages
>> d2c72b3e20 Trac #27404: py3: fix some __format__ failures
>> c8b8488a19 Trac #27146: Speed up initialization code for partitions
>> b920e86002 Trac #27403: pplpy full build failure
>> d25257113b Trac #27376: missing link in doc of 
>> sage.geometry.polyhedron.base.Polyhedron_base.face_fa
>> dcfad21666 Trac #27394: fixing minor javascript issues in our graph_plot_js
>> bdea1c0b92 Trac #27392: the omega-signature of knots and links
>> a98d47a6d5 Trac #27390: Py3: test_class_pickling.py fix method resolution 
>> order error
>> 45aa76cd03 Trac #27382: enhance conversion of sparse matrices to magma
>> 6abccaec4c Trac #27368: Allow supercrystals category to be inherited by 
>> default for subcrystals
>> 28e0168130 Trac #27367: Upgrade to mpfrcx 0.5
>> f1eb5ab84b Trac #27352: Add checks for matrix multiplication
>> eac49eca05 Trac #27188: kenzo package and interface
>> 28cb214798 Trac #27170: py3: fix 14 doctests in digraph.py
>> cb41fef124 Trac #25894: Add subgroup method to MatrixGroup_base
>> 02db0fd7bb Trac #27388: spkg installation: convert read-only files to 
>> owner-writable
>> b899c12910 Trac #27124: File manifests complete broken on OSX
>> 2f926c717f Trac #26930: add GAP io and crypting pkgs
>> c59b6881d8 (tag: 8.7.beta6) Updated SageMath version to 8.7.beta6
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.

Re: [sage-release] Sage 8.7.beta5 released

[E. Madison Bray]

On Mon, Feb 25, 2019 at 4:04 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> I can not reproduce the error. What is the configuration of
> your machine?
>
> The comparison routine in QQbar that is called
> (cmp_elements_with_same_minpoly) assumes that the elements
> a and b have the same minimal polynomial p. But the error message
> is weird as it does not seem to be the case.  The only roots of p
> that looks like a and b are the following pair of conjugates
>
>   2.917983368234029?e15 - 1.630474617080222?e18*I
>   2.917983368234029?e15 + 1.630474617080222?e18*I
>
> But the imaginary part is non-trivial! It seems that a and b
> that appears in the error are here the *real part* of some roots
> but not roots.
>
> It would be helpful if you could provide more data (ie via pdb or
> adding prints in qqbar.py). More precisely at lines 3367 (qqbar.py)
> the values and types of
>   * sd._left._descr
>   * sd._right._descr
>   * sd._op
> and also at lines 3372 the values of the polynomials
>   * lp
>   * rp
>
> (the datatype of an element in QQbar is mostly a tree and
> in the current situation sd._left and sd._right are the
> two subtrees)
>
> Ideally, it should be possible to reconstruct the element that
> triggers the error... you can try to print a sage_input(self)
> in the __bool__ method (line 3367).


Thank you for taking the time to look into this, and I apologize for
that because I just found that it was a false alarm: I apparently
somehow (despite just having rebuilt it) wound up with a
partially-broken PARI, at least I think.  After a manual `rm -f
local/lib/*pari*` and rebuilding pari, cypari, and their dependents
everything is fixed now.

Of course, that could indicate a bug in the build system, but I'm not
sure now how I would reproduce the situation.  This arose in part
because I was playing around with
https://trac.sagemath.org/ticket/27267



> Le 25/02/2019 à 15:39, E. Madison Bray a écrit :
> > On Mon, Feb 25, 2019 at 3:36 PM E. Madison Bray  
> > wrote:
> >>
> >> On Ubuntu 14.04 I am getting a strange error when trying to build the
> >> docs.  Tried `make doc-clean` to no avail:
> >
> > Also, when I try running the tests for
> > sage.categories.finite_coxeter_groups I get the same failure at:
> >
> > sage -t src/sage/categories/finite_coxeter_groups.py
> > **
> > File "src/sage/categories/finite_coxeter_groups.py", line 725, in
> > sage.categories.finite_coxeter_groups.FiniteCoxeterGroups.ParentMethods.permutahedron
> > Failed example:
> >  W.permutahedron()
> >
> > Followed with a long traceback, the relevant portion being:
> >
> >  W.permutahedron()
> >File 
> > "/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/categories/finite_coxeter_groups.py",
> > line 765, in permutahedron
> >  return Polyhedron(vertices=vertices, base_ring=base_ring)
> >File 
> > "/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/constructor.py",
> > line 600, in Polyhedron
> >  return parent(Vrep, Hrep, convert=convert, verbose=verbose)
> >File "sage/structure/parent.pyx", line 901, in
> > sage.structure.parent.Parent.__call__
> > (build/cythonized/sage/structure/parent.c:9205)
> >  return mor._call_with_args(x, args, kwds)
> >File "sage/structure/coerce_maps.pyx", line 181, in
> > sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args
> > (build/cythonized/sage/structure/coerce_maps.c:5076)
> >  raise
> >File "sage/structure/coerce_maps.pyx", line 176, in
> > sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args
> > (build/cythonized/sage/structure/coerce_maps.c:4964)
> >  return C._element_constructor(x, *args, **kwds)
> >File 
> > "/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/parent.py",
> > line 517, in _element_constructor_
> >  return self.element_class(self, Vrep, Hrep, **kwds)
> >File 
> > "/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/backend_field.py",
> > line 177, in __init__
> >  super(Polyhedron_field, self).__init__(parent, Vrep, Hrep, **kwds)
> >File 
> > "/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base.py",
> > line 124, in __init__
> >  self._init_from_V

Re: [sage-release] Sage 8.7.beta5 released

[E. Madison Bray]

On Mon, Feb 25, 2019 at 3:36 PM E. Madison Bray  wrote:
>
> On Ubuntu 14.04 I am getting a strange error when trying to build the
> docs.  Tried `make doc-clean` to no avail:

Also, when I try running the tests for
sage.categories.finite_coxeter_groups I get the same failure at:

sage -t src/sage/categories/finite_coxeter_groups.py
**
File "src/sage/categories/finite_coxeter_groups.py", line 725, in
sage.categories.finite_coxeter_groups.FiniteCoxeterGroups.ParentMethods.permutahedron
Failed example:
W.permutahedron()

Followed with a long traceback, the relevant portion being:

W.permutahedron()
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/categories/finite_coxeter_groups.py",
line 765, in permutahedron
return Polyhedron(vertices=vertices, base_ring=base_ring)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/constructor.py",
line 600, in Polyhedron
return parent(Vrep, Hrep, convert=convert, verbose=verbose)
  File "sage/structure/parent.pyx", line 901, in
sage.structure.parent.Parent.__call__
(build/cythonized/sage/structure/parent.c:9205)
return mor._call_with_args(x, args, kwds)
  File "sage/structure/coerce_maps.pyx", line 181, in
sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args
(build/cythonized/sage/structure/coerce_maps.c:5076)
raise
  File "sage/structure/coerce_maps.pyx", line 176, in
sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args
(build/cythonized/sage/structure/coerce_maps.c:4964)
return C._element_constructor(x, *args, **kwds)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/parent.py",
line 517, in _element_constructor_
return self.element_class(self, Vrep, Hrep, **kwds)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/backend_field.py",
line 177, in __init__
super(Polyhedron_field, self).__init__(parent, Vrep, Hrep, **kwds)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base.py",
line 124, in __init__
self._init_from_Vrepresentation(vertices, rays, lines, **kwds)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/backend_field.py",
line 208, in _init_from_Vrepresentation
H = Vrep2Hrep(self.base_ring(), self.ambient_dim(), vertices,
rays, lines)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description_inhomogeneous.py",
line 446, in __init__
DD = Algorithm(A).run()
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 764, in run
DD.add_inequality(a)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 715, in add_inequality
if not self.are_adjacent(rp, rn):
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 447, in are_adjacent
Z = self.zero_set(r1).intersection(self.zero_set(r2))
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 375, in zero_set
t.update(self.A[i] for i in range(n,len(self.A)) if
self.A[i].inner_product(ray) == self.zero)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 375, in 
t.update(self.A[i] for i in range(n,len(self.A)) if
self.A[i].inner_product(ray) == self.zero)
  File "sage/structure/element.pyx", line 1091, in
sage.structure.element.Element.__richcmp__
(build/cythonized/sage/structure/element.c:9923)
return (self)._richcmp_(other, op)
  File "sage/structure/element.pyx", line 1095, in
sage.structure.element.Element._richcmp_
(build/cythonized/sage/structure/element.c:10030)
cpdef _richcmp_(left, right, int op):
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/rings/qqbar.py",
line 4641, in _richcmp_
return bool(self) == (op == op_NE)
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/rings/qqbar.py",
line 3376, in __bool__
c = cmp_elements_with_same_minpoly(left, right, left.minpoly())
  File 
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/rings/qqbar.py",
line 2225, in cmp_elements_with_same_minpoly
  

Re: [sage-release] Sage 8.7.beta5 released

[E. Madison Bray]

On Ubuntu 14.04 I am getting a strange error when trying to build the
docs.  Tried `make doc-clean` to no avail:

[dochtml] [categorie]
/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/categories/finite_coxeter_groups.py:docstring
of 
sage.categories.finite_coxeter_groups.FiniteCoxeterGroups.ParentMethods.permutahedron:50:
WARNING: Exception occurred in plotting finite_coxeter_groups-1
[dochtml] [categorie]  from
/home/embray/src/sagemath/sage/src/doc/en/reference/categories/sage/categories/finite_coxeter_groups.rst:
[dochtml] [categorie] Traceback (most recent call last):
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/matplotlib/sphinxext/plot_directive.py",
line 524, in run_code
[dochtml] [categorie] six.exec_(code, ns)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/six.py",
line 709, in exec_
[dochtml] [categorie] exec("""exec _code_ in _globs_, _locs_""")
[dochtml] [categorie]   File "", line 1, in 
[dochtml] [categorie]   File "", line 2, in 
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/categories/finite_coxeter_groups.py",
line 765, in permutahedron
[dochtml] [categorie] return Polyhedron(vertices=vertices,
base_ring=base_ring)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/constructor.py",
line 600, in Polyhedron
[dochtml] [categorie] return parent(Vrep, Hrep, convert=convert,
verbose=verbose)
[dochtml] [categorie]   File "sage/structure/parent.pyx", line 901, in
sage.structure.parent.Parent.__call__
(build/cythonized/sage/structure/parent.c:9205)
[dochtml] [categorie] return mor._call_with_args(x, args, kwds)
[dochtml] [categorie]   File "sage/structure/coerce_maps.pyx", line
181, in sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args
(build/cythonized/sage/structure/coerce_maps.c:5076)
[dochtml] [categorie] raise
[dochtml] [categorie]   File "sage/structure/coerce_maps.pyx", line
176, in sage.structure.coerce_maps.DefaultConvertMap_unique._call_with_args
(build/cythonized/sage/structure/coerce_maps.c:4964)
[dochtml] [categorie] return C._element_constructor(x, *args, **kwds)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/parent.py",
line 517, in _element_constructor_
[dochtml] [categorie] return self.element_class(self, Vrep, Hrep, **kwds)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/backend_field.py",
line 177, in __init__
[dochtml] [categorie] super(Polyhedron_field,
self).__init__(parent, Vrep, Hrep, **kwds)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base.py",
line 124, in __init__
[dochtml] [categorie] self._init_from_Vrepresentation(vertices,
rays, lines, **kwds)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/backend_field.py",
line 208, in _init_from_Vrepresentation
[dochtml] [categorie] H = Vrep2Hrep(self.base_ring(),
self.ambient_dim(), vertices, rays, lines)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description_inhomogeneous.py",
line 446, in __init__
[dochtml] [categorie] DD = Algorithm(A).run()
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 764, in run
[dochtml] [categorie] DD.add_inequality(a)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 715, in add_inequality
[dochtml] [categorie] if not self.are_adjacent(rp, rn):
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 447, in are_adjacent
[dochtml] [categorie] Z = self.zero_set(r1).intersection(self.zero_set(r2))
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 375, in zero_set
[dochtml] [categorie] t.update(self.A[i] for i in
range(n,len(self.A)) if self.A[i].inner_product(ray) == self.zero)
[dochtml] [categorie]   File
"/home/embray/src/sagemath/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/double_description.py",
line 375, in 
[dochtml] [categorie] t.update(self.A[i] for i in
range(n,len(self.A)) if self.A[i].inner_product(ray) == self.zero)
[dochtml] [categorie]   File "sage/structure/element.pyx", line 1091,
in sage.structure.element.Element.__richcmp__
(build/cythonized/sage/structure/element.c:9923)
[dochtml] 

Re: [sage-release] Sage 8.7.beta3 released

[E. Madison Bray]

I am getting some mysterious new segfaults with this on Cygwin.

On Fri, Feb 8, 2019 at 8:27 PM 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
>
>
> 832b97cd5d (tag: 8.7.beta3) Updated SageMath version to 8.7.beta3
> 732781e392 Trac #27193: point doc to an installed folder rather a source one 
> in sage/homology/simplicial_set_examples.py
> 365c4a4fb2 Trac #26906: Fix broken pinfo magic for interface functions
> f3b620f323 Trac #26722: py3: work on the sandpile problem
> 284e75ede1 Trac #25962: Upgrade to FriCAS 1.3.5
> d122a72346 Trac #24889: Enumerate all genera of given signature, determinant 
> and bounded scale of a jordan block.
> dfcf0d5b4b Trac #18015: Empty graph latex fails
> 4fdf69cb24 Trac #27223: Fix legacy uninstall
> d1a99e13be Trac #27224: Fix invalid uses of sig_on() in matrix.misc
> 74b4badf39 Trac #27140: make_any_gap_element() should not be called inside 
> sig_on()
> 700570de6b Trac #27155: Fix and simplify libGAP error handling
> 3e7302b9be Trac #26992: Fix new (lib) gap on py3
> 337b33aea8 Trac #27178: Thematic tutorials: minor fix
> 2381df317e Trac #27136: pep8 in digraph_generators.py (part 3)
> 061a22b6cf Trac #27134: pep8 in digraph_generators.py (part 1)
> 9d1810060f Trac #27133: improve butterfly graph generator
> ea7cdd816e Trac #27120: remove some duplicate imports
> 57a651d1e1 Trac #27067: py3: Simplicial complexes: fix is_isomorphic
> 3b81a6eadb Trac #27210: py3: fix doctests in partition_kleshchev
> f2ca22fefa Trac #27207: py3: one partial fix for KR crystals
> 8f7371c7e4 Trac #27202: py3: fix doctests in random graphs generators
> 5ea4bf4435 Trac #27192: Make the default picklejar location a user location 
> rather than a, potentially, system one
> 12a4395281 Trac #27182: spkg-configure.m4 for bzip2
> ecfe146ef4 Trac #27152: Make the meataxe wrapper work with py3
> 3f39df0203 Trac #26787: Force C++11  as the C++ standard
> 42958e96f3 Trac #26639: geometry/cone.py: use generator expressions and 
> future-proof range() iterator
> 7f44846a50 Trac #26315: Upgrade to Giac 1.5
> b34ec0e2d1 Trac #26009: Add derivative method for SBox
> 9930e0045e Trac #25674: Upgrade R to 3.5.2
> 0f94d82ff7 Trac #10501: Deprecate adjoint in favor of adjugate
> 1318f4cd99 Trac #27209: py3: fix tests/stl_vector
> 5a8e94f639 Trac #27206: py3: some details in misc
> 7a26af9366 Trac #27203: py3: fix 8 doctests in generators/families.py
> 28b8821aa5 Trac #27201: Rename abs to __abs__ for UniversalCyclotomicField 
> elements
> d309824905 Trac #27200: update sagenb to version 1.1.2
> 3add2d91d8 Trac #27194: Py3: fix some doctests in riemann_surface
> 115a4e113a Trac #27191: Use SAGE_LIB instead of of a path derived from 
> SAGE_LOCAL in sage/doctest/sources.py
> feb8acf9b8 Trac #27189: Standardise access to SAGE_DOC_SRC in src/doc/
> 0fb443c087 Trac #27187: py3: tiny fix in src/doc/common/conf.py
> 5b40b509bd Trac #27184: py3: fix doctests in generic_graph (part 6) -- 
> graphviz_string
> 16edf19a9d Trac #27181: py3: fix doctest in generic_graph (part 4)
> e3021c8436 Trac #27180: py3: fix doctest in generic_graph (part 3) -- 
> _build_flow_graph
> 6dc3588cfd Trac #27177: py3: some fixes in Heilbronn matrices
> bef07442aa Trac #27172: 1 optional doctest failing in cmdline.py related to 
> pandoc
> fdd4c724db Trac #27169: Upgrade to FreeType 2.9.1
> f0b0e54d32 Trac #27167: py3: fix doctest in distances_all_pairs.pyx
> a9e1dedaf5 Trac #27166: remove deprecated classes NetworkXGraphDeprecated and 
> NetworkXDiGraphDeprecated
> 33e42fd77d Trac #27159: py3: fix doctests in strongly_regular_db.pyx
> f257f6 Trac #27158: py3: fix doctests in boost_graph.pyx
> 6505206560 Trac #27157: py3 fixes in interacts
> 3cd33bf32d Trac #27156: Update README now that `make` works with Python 3
> 151bc1c2e0 Trac #27153: py3: simplicial complex tests involving the 
> Stanley-Reisner ring
> 5fd1bc63c8 Trac #27151: py3: fix doctests in vertex_separation.pyx
> 86bc701284 Trac #27149: py3: fix doctests in comparability.pyx
> d1c9bf163c Trac #27148: py3: fix doctests in centrality.pyx
> cb0c55968d Trac #27147: py3: fix doctests in dense_graph.pyx, 
> sparse_graph.pyx, static_sparse_graph.pyx
> 4daa3d432d Trac #27145: py3: some fixes in modular/
> 8ddfaa04dd Trac #27144: py3: fix doctests in connectivity.pyx
> 16795e0a1d Trac #27142: bunch of various bad things
> f6510fbf56 Trac #27141: Fix for conversion of Gamma function in Mathematica 
> interface
> 18a12b81a2 Trac #27129: py3: fix other doctests in graph.py
> 25340496e6 Trac #27128: avoid splitting the problem if ncpus=1 in 
> dancing_links
> 15669534de Trac #27117: Doctest Jupyter implementation of interact library
> 10125fd570 Trac #27072: py3: final fix for species
> a8f8a4a98b Trac #27069: Inconsistent behavior with generator ordering in free 
> Lie algebras
> 69459af0c8 Trac #27066: deprecate a few commands in 

Re: [sage-release] Sage 8.7.beta1 released

[E. Madison Bray]

On Sun, Jan 27, 2019 at 1:18 AM 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

I am getting a hang / possible error during doc building on Cygwin.
Not sure if it started here, or in beta0, though I'm pretty sure beta0
worked for me.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.7.beta0 released

[E. Madison Bray]

On Thu, Jan 24, 2019 at 9:40 AM  wrote:
>
> I have the same issue with libffi !

I will look into that ASAP.  It's a similar / related problem to
https://trac.sagemath.org/ticket/26996 but affecting libffi.  The
install target for libffi might even depend on your compiler's
settings, which might explain why this didn't happen (at least that
I'm aware) on Debian-based distros where gcc does not install
libraries to ${prefix}/lib64.

Also, if you have your system's libffi-devel package installed and
it's recent enough, Sage's ./configure should detect it and skip
trying to install the libffi SPKG altogether.

> Le jeudi 24 janvier 2019 06:08:53 UTC+1, Steven Trogdon a écrit :
>>
>> Problem building libffi-3.2.1 on gentoo
>>
>> cp: cannot overwrite non-directory 
>> '/64bitdev/storage/sage-git_develop/sage/local/./lib64' with directory 
>> '/64bitdev/storage/sage-git_develop/sage/local/var/tmp/sage/build/libffi-3.2.1/inst/64bitdev/storage/sage-git_develop/sage/local/./lib64'
>> 
>> Error copying files for libffi-3.2.1.
>> 
>>
>> /64bitdev/storage/sage-git_develop/sage/local/./lib64
>>
>> is a symlink
>>
>> ls -al /64bitdev/storage/sage-git_develop/sage/local/./lib64
>> lrwxrwxrwx 1 strogdon math 3 Jan 13  2016 
>> /64bitdev/storage/sage-git_develop/sage/local/./lib64 -> lib
>>
>> On Wednesday, January 23, 2019 at 2:47:49 PM UTC-6, 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
>>>
>>> 5389d8dc87 (tag: 8.7.beta0, trac/develop) Updated SageMath version to 
>>> 8.7.beta0
>>> 36ec29e57d Trac #26969: Misc pip upgrades
>>> 79cf5c980d Trac #27023: fix missing ::
>>> a4dd7deefc Trac #27020: OpenBLAS 0.3.5
>>> e60f32bb91 Trac #27017: Remove sage.schemes.elliptic_curves.padics from 
>>> documentation
>>> 4fb44bc920 Trac #27014: Deprecate sage.misc.misc.uniq
>>> c128368a45 Trac #27013: py3: some care for Hadamard matrices
>>> 6521233113 Trac #27010: py3: avoid .vertices() in methods _ford_fulkerson, 
>>> edge_cut, bounded_outdegree_orientation and gomory_hu_tree
>>> 58d9680bbe Trac #27009: py3: avoid sorting vertices and edges in method 
>>> treewidth
>>> 1ad58d2bb9 Trac #27008: py3: avoid .vertices() in method apex_vertices
>>> 010e1e893b Trac #27007: py3: avoid .vertices() in planarity.pyx
>>> c14dc9c46f Trac #27005: wrong libgap conversion for matrices over QQ['x']
>>> 7123d7504d Trac #27003: _iterator_weight should not sort
>>> 48484ef69d Trac #27002: autodoc: use __qualname__ on Python 3
>>> 57c5c40661 Trac #26999: 1 optional gurobi doctest failing
>>> ee7ed3c076 Trac #26998: py3 fix last 4 failing doctests in combinat/posets
>>> 23f806cad2 Trac #26997: 5 internet doctests failing in findstat.py
>>> 0698bfb999 Trac #26995: Upgrade to Pynac-0.7.23
>>> 619281186a Trac #23222: Add test to EllipticCurve.isogeny() to check for 
>>> validity of kernel polynomials
>>> 4f560b02dc Trac #26988: py3: one tiny fix for isidentifier
>>> 90c3b31954 Trac #26985: some work on cluster mutation
>>> ee2d9c5657 Trac #26981: fix trac ticket number in deprecation warning
>>> 24186b661f Trac #26967: py3: some work on modular/modform_hecketriangle/
>>> 2f73854033 Trac #26958: Inheriting from MPolynomialRing_libsingular crashes 
>>> sage
>>> 319b7ac911 Trac #26943: Giac support for term orders and elimination
>>> 537b91840d Trac #26938: IncidenceStructure breaks if points cannot be sorted
>>> 37065d12db Trac #26936: WordMorphism: domain/codomain should be sortable if 
>>> not given
>>> cdab354eeb Trac #26933: Subsets_s should support unsortable sets
>>> 6a818ec5e1 Trac #26917: py3: some fix in set_partition
>>> be09cc219f Trac #26864: Indentation error in Number Field
>>> a915a3ab1a Trac #26839: RealLazyField: converting constants in an 
>>> expression to float
>>> cefb74fd8c Trac #26834: pep8 cleaning in vertex_separation.pyx
>>> c6125397b3 Trac #26810: Permutations(avoiding=[[1,3,2]]) returns all 
>>> permutations
>>> 52633235e2 Trac #26809: Wrong contains in Permutations avoiding a pattern
>>> 33ec2f8202 Trac #26516: Wrong sig_on_count in SharedMeatAxe
>>> faab330692 Trac #26361: Glucose SAT solver
>>> ce239b2e40 Trac #26183: doctest: tolerance parsing and ellipses
>>> 580c25bd1c Trac #26156: 0.0 is printed with too many digits
>>> ddfe6f3a20 Trac #25931: changes to partition for k combinat
>>> 08166d10a2 Trac #25900: Package libffi
>>> 35931ca890 Trac #25865: fast iterator for set partitions with given block 
>>> sizes
>>> 7aa39995c5 Trac #25480: Upgrade to cryptominisat 5.6.6 (and make it an 
>>> optional package again)
>>> 41153919eb Trac #25384: Let `sage --jupyter` call the Jupyter in Sage
>>> ec0b3f610b Trac #25147: Add DESTDIR support for boost_cropped
>>> a3ee80c6cb Trac #25143: Add DESTDIR support for pari
>>> 137ad44b65 

Re: [sage-release] Re: Sage 8.6.rc1 released

[E. Madison Bray]

On Mon, Jan 14, 2019 at 8:35 PM Volker Braun  wrote:
>
> So I take it you volunteer to maintain the py3 buildbot configuration?

No, I do not.  It's not my buildbot and I don't have control over that
infrastructure as your follow-up message makes clear:

> The buildbot physically moved this week, it might take some more time to set 
> up all networking

Making suggestions for how best to handle an issue is not a volunteer
to handle that issue, especially if isn't practical to do so, and
suggesting otherwise is a kind of passive aggressiveness.  If you
disagree you can just openly disagree, though I believe my suggestion
is one that requires the least work for everyone involved (since it's
merely a question of what arguments to pass to perform the tests).

> On Monday, January 14, 2019 at 11:45:20 AM UTC+1, E. Madison Bray wrote:
>>
>> In fact I'd argue it doesn't even require a Makefile target,
>> as the relevant buildbot(s) for Python 3 can be configured to run that
>> command (though having a list checked into the repository is useful,
>> whether it's positive (list of known passing) or negative (list of
>> known failures).
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.6.rc1 released

[E. Madison Bray]

On Sat, Jan 12, 2019 at 9:56 PM 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
>
> The final 8.6 should follow real soon, so please give it a whirl!
>
> 62fe3948ea (tag: 8.6.rc1, trac/develop) Updated SageMath version to 8.6.rc1
> 4c97235a2c Trac #26001: Upgrade p_group_cohomology to version 3.1
> e9df9ef053 Trac #26326: Upgrade networkx to 2.2, add self tests, and update 
> random seed format
> 71f5ae815c (tag: 8.6.rc0) Updated SageMath version to 8.6.rc0

Speaking of which, I haven't been able to connect to the OSX buildbot
in like a week.  Previously I couldn't even ping it; now it appears to
respond to pings, but I can't SSH into it on the port you previously
gave me.

I assumed you were just AFK or something so I didn't want to bother
you about it until now :)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.6.rc1 released

[E. Madison Bray]

On Sun, Jan 13, 2019 at 5:18 PM Volker Braun  wrote:
>
> Frederic, if can you make #26740 work then I'll merge it (no matter what Eric 
> says ;-)

As I last pointed out on that ticket it doesn't even require any code
changes.  In fact I'd argue it doesn't even require a Makefile target,
as the relevant buildbot(s) for Python 3 can be configured to run that
command (though having a list checked into the repository is useful,
whether it's positive (list of known passing) or negative (list of
known failures).  Both have their uses.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.5.beta5 released

[E. Madison Bray]

On Mon, Nov 26, 2018 at 5:37 AM Steven Trogdon  wrote:
>
> On my Gentoo changing the ownership was not sufficient. After changing the 
> ownership I had to
>
> git reset --hard HEAD
>
> which revealed that
>
> Updating f894105d0d..b36eca1990
> error: The following untracked working tree files would be overwritten by 
> merge:
>
> To correct this:
>
> git clean -f build/pkgs/barvinok/
> git clean -f build/pkgs/isl/
> git clean -f build/pkgs/lcalc/patches/
> git clean -f build/pkgs/polylib/
>
> and now 'git pull' is up to date. This is all very strange.

At some point you probably did *something* as root (and by "you" it
might not have even been an action you personally took, but maybe some
cron job you forgot about; who knows).  But otherwise I don't think
there's any way that would have happened.  This happens to me too
sometimes ¯\_(ツ)_/¯  Git repos don't store anything about uid/gid of
files (that would be disastrous); in fact IIRC the only information it
stores about file permissions is whether or not the executable bit
should be set.


> On Sunday, November 25, 2018 at 9:41:58 PM UTC-6, Samuel Lelievre wrote:
>>
>> > As far as I can recall 'git pull' was always done as a normal user.
>> > Note the timestamp on the folders, which predates 8.5.beta4.
>> > And this issue did not manifest itself then. But going forward,
>> > how to correct things?
>>
>> Change to your SAGE_ROOT directory and run this as a normal user
>>
>> $ sudo chown -v -R $(id -u):$(id -g) .
>>
>> to set the owner and group of SAGE_ROOT (and recursively all
>> the included files and directories) to your user and your group.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-release@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.