[sage-release] Re: Sage 10.4.beta9 released
In general, I wish that some labels weigh in the release process: - p: blocker -- added in release candidate stage; should be merged before the stable release - p: critical -- added in beta stage; best to be merged before the next beta release -- 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/c295b7f4-93df-4b33-bb96-bac57f6a32a3n%40googlegroups.com.
[sage-release] Re: xz/liblzma has been compromised
Thanks! -- 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/276e3933-d580-4d1a-b243-2c5a27e90943n%40googlegroups.com.
[sage-release] Re: Sage 10.3.rc2 released
I set https://github.com/sagemath/sage/pull/37390 to blocker. Please merge #37390 to the next rc. -- 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/8b65c1ed-1ea5-40b0-a4ed-7feec1119aa8n%40googlegroups.com.
[sage-release] Re: Sage 10.2 released
Congrats! -- 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/c99b5580-e542-4cd5-9a61-2da071078e60n%40googlegroups.com.
[sage-release] Re: Sage 10.2.beta3 released
Succeeded after sage -pip install meson-python. On Sunday, September 17, 2023 at 6:52:59 AM UTC+9 Kwankyu Lee wrote: > Incremental build failed > > [scipy-1.11.2] > [..] > [scipy-1.11.2] scipy-1.11.2 > [scipy-1.11.2] > [sagelib-10.2.beta3] Removing file or directory > /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link > [sagelib-10.2.beta3] Removing pth entries from > /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth: > [sagelib-10.2.beta3] Removing entry: > /Users/kwankyu/GitHub/sage-dev/src > [sagelib-10.2.beta3] Successfully uninstalled > sagemath-standard-10.2b3 > [sagelib-10.2.beta3] Running setup.py develop for sagemath-standard > [sagelib-10.2.beta3] Running command python setup.py develop > [scipy-1.11.2] Setting up build directory for scipy-1.11.2 > [scipy-1.11.2] Finished extraction > [scipy-1.11.2] Applying patches from ../patches... > [scipy-1.11.2] Applying ../patches/numpy-include.patch > [scipy-1.11.2] patching file scipy/spatial/setup.py > [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines). > [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch > [scipy-1.11.2] patching file scipy/datasets/meson.build > [scipy-1.11.2] > [scipy-1.11.2] Host system: > [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 22.6.0: > Wed Jul 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64 > [scipy-1.11.2] > [scipy-1.11.2] C compiler: gcc > [scipy-1.11.2] C compiler version: > [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1) > [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0 > [scipy-1.11.2] Thread model: posix > [scipy-1.11.2] InstalledDir: /Library/Developer/CommandLineTools/usr/bin > [scipy-1.11.2] > [scipy-1.11.2] Package 'scipy' is currently not installed > [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do > [scipy-1.11.2] Installing scipy-1.11.2 > [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading from > the cache of locally built wheels. In the future --no-binary will not > influence the wheel cache. pip 23.1 will enforce this behaviour change. A > possible replacement is to use the --no-cache-dir option. You can use the > flag --use-feature=no-binary-enable-wheel-cache to test the upcoming > behaviour. Discussion can be found at > https://github.com/pypa/pip/issues/11453 > [scipy-1.11.2] Processing > /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/var/tmp/sage/build/scipy-1.11.2/src > [scipy-1.11.2] Preparing metadata (pyproject.toml): started > [scipy-1.11.2] Running command Preparing metadata (pyproject.toml) > [scipy-1.11.2] Preparing metadata (pyproject.toml): finished with status > 'done' > [scipy-1.11.2] ERROR: Exception: > [scipy-1.11.2] Traceback (most recent call last): > [scipy-1.11.2] File > "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", > > line 160, in exc_logging_wrapper > [scipy-1.11.2] status = run_func(*args) > [scipy-1.11.2] File > "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", > > line 247, in wrapper > [scipy-1.11.2] return func(self, options, args) > [scipy-1.11.2] File > "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/commands/wheel.py", > > line 170, in run > [scipy-1.11.2] requirement_set = resolver.resolve(reqs, > check_supported_wheels=True) > [scipy-1.11.2] File > "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", > > line 73, in resolve > [scipy-1.11.2] collected = > self.factory.collect_root_requirements(root_reqs) > [scipy-1.11.2] File > "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/factory.py", > > line 491, in collect_root_requirements > [scipy-1.11.2] req = self._make_requirement_from_install_req( > [scipy-1.11.2] File > "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/res
[sage-release] Re: Sage 10.2.beta3 released
Incremental build failed [scipy-1.11.2] [..] [scipy-1.11.2] scipy-1.11.2 [scipy-1.11.2] [sagelib-10.2.beta3] Removing file or directory /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/sagemath-standard.egg-link [sagelib-10.2.beta3] Removing pth entries from /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/easy-install.pth: [sagelib-10.2.beta3] Removing entry: /Users/kwankyu/GitHub/sage-dev/src [sagelib-10.2.beta3] Successfully uninstalled sagemath-standard-10.2b3 [sagelib-10.2.beta3] Running setup.py develop for sagemath-standard [sagelib-10.2.beta3] Running command python setup.py develop [scipy-1.11.2] Setting up build directory for scipy-1.11.2 [scipy-1.11.2] Finished extraction [scipy-1.11.2] Applying patches from ../patches... [scipy-1.11.2] Applying ../patches/numpy-include.patch [scipy-1.11.2] patching file scipy/spatial/setup.py [scipy-1.11.2] Hunk #1 succeeded at 39 (offset -1 lines). [scipy-1.11.2] Applying ../patches/tests_no_internet_dependency.patch [scipy-1.11.2] patching file scipy/datasets/meson.build [scipy-1.11.2] [scipy-1.11.2] Host system: [scipy-1.11.2] Darwin Helios.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64 [scipy-1.11.2] [scipy-1.11.2] C compiler: gcc [scipy-1.11.2] C compiler version: [scipy-1.11.2] Apple clang version 14.0.3 (clang-1403.0.22.14.1) [scipy-1.11.2] Target: x86_64-apple-darwin22.6.0 [scipy-1.11.2] Thread model: posix [scipy-1.11.2] InstalledDir: /Library/Developer/CommandLineTools/usr/bin [scipy-1.11.2] [scipy-1.11.2] Package 'scipy' is currently not installed [scipy-1.11.2] No legacy uninstaller found for 'scipy'; nothing to do [scipy-1.11.2] Installing scipy-1.11.2 [scipy-1.11.2] DEPRECATION: --no-binary currently disables reading from the cache of locally built wheels. In the future --no-binary will not influence the wheel cache. pip 23.1 will enforce this behaviour change. A possible replacement is to use the --no-cache-dir option. You can use the flag --use-feature=no-binary-enable-wheel-cache to test the upcoming behaviour. Discussion can be found at https://github.com/pypa/pip/issues/11453 [scipy-1.11.2] Processing /Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/var/tmp/sage/build/scipy-1.11.2/src [scipy-1.11.2] Preparing metadata (pyproject.toml): started [scipy-1.11.2] Running command Preparing metadata (pyproject.toml) [scipy-1.11.2] Preparing metadata (pyproject.toml): finished with status 'done' [scipy-1.11.2] ERROR: Exception: [scipy-1.11.2] Traceback (most recent call last): [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 160, in exc_logging_wrapper [scipy-1.11.2] status = run_func(*args) [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 247, in wrapper [scipy-1.11.2] return func(self, options, args) [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/commands/wheel.py", line 170, in run [scipy-1.11.2] requirement_set = resolver.resolve(reqs, check_supported_wheels=True) [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 73, in resolve [scipy-1.11.2] collected = self.factory.collect_root_requirements(root_reqs) [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 491, in collect_root_requirements [scipy-1.11.2] req = self._make_requirement_from_install_req( [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 453, in _make_requirement_from_install_req [scipy-1.11.2] cand = self._make_candidate_from_link( [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/factory.py", line 206, in _make_candidate_from_link [scipy-1.11.2] self._link_candidate_cache[link] = LinkCandidate( [scipy-1.11.2] File "/Users/kwankyu/GitHub/sage-dev/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/candidates.py", line 297, in
[sage-release] Re: Sage 10.1.beta9 released
Thanks a lot! -- 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/e9321fde-2fd9-4823-a03e-45ef779e2f20n%40googlegroups.com.
[sage-release] Re: Sage 10.1.beta7 released
#35919 and #35951 merged here are dependent on #35749 not merged yet. #35749 is ready to be merged. It's a mistake that #35919 and #35951 did not declare #35749 as a dependency. -- 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/6c77a024-8edc-4d3d-a634-f36fbc944a58n%40googlegroups.com.
[sage-release] Re: Sage 10.0 released
Congratulations! On Sunday, May 21, 2023 at 8:10:07 AM UTC+9 Volker Braun wrote: The "master" git branch has been updated to Sage-10.0. 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 As you are undoubtedly aware, this version is the first since the migration of the development process to github. A big thanks to everyone who was involved, we couldn't have done it without you 6ba0eafc2ca (tag: 10.0, github/develop) Updated SageMath version to 10.0 8476c469588 gh-35460: Update developer guide for workflows on github 4ed2157cd2a gh-35638: build/pkgs/python3/spkg-configure.m4: Add depcheck for zlib 9de8c5b1b6c gh-35637: remark that WSL needs a lot of RAM f2f5863c08a (tag: 10.0.rc3) Updated SageMath version to 10.0.rc3 -- 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/5da1b099-1213-4de0-b158-c25729d8ac43n%40googlegroups.com.
[sage-release] Re: Sage 10.0.rc3 released
On Tuesday, May 16, 2023 at 6:13:03 AM UTC+9 John H Palmieri wrote: I consistently see these failures on various OS X machines: sage -t --long --random-seed=244618093388694547212515065258622925284 src/sage/rings/polynomial/multi_polynomial_ideal.py # 1 doctest failed sage -t --long --random-seed=244618093388694547212515065258622925284 src/sage/libs/giac/__init__.py # Timed out I've seen these reported after earlier releases. Is there a ticket? For me, they pass with SageMath version 10.0.rc2. I am on macOS 12.6.5 with Intel Xeon E5. What is the failed doctest? -- 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/bb69b617-02fd-482d-ab02-20e4c6f7412bn%40googlegroups.com.
[sage-release] Sage 10.0 Release Tour
The release tour for the upcoming 10.0 release is at https://github.com/sagemath/sage/wiki/Sage-10.0-Release-Tour and needs your care. -- 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/57479061-fb81-4c86-8bfe-370f2d48fb55n%40googlegroups.com.
[sage-release] Re: Sage 10.0.beta1 released
Congratulations for the first release on GitHub! > We haven't quite settled on what I'll do with positively reviewed tickets that end up not building correctly ... My current plan is to re-request review, i.e. reset the approval of the reviewer(s). > > Also, the de-facto "positive review" criterion is for now: at least one approve, and no outstanding request for changes. All seem reasonable. -- 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/0d443474-d8af-40c0-bb4c-e1eb9459bf7fn%40googlegroups.com.
[sage-release] Re: Sage 10.0.beta1 released
Congratulations for the first release on GitHub! We haven't quite settled on what I'll do with positively reviewed tickets that end up not building correctly ... My current plan is to re-request review, i.e. reset the approval of the reviewer(s). Also, the de-facto "positive review" criterion is for now: at least one approve, and no outstanding request for changes. All seem reasonable. -- 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/fe8e7ed3-62d5-400a-8861-5374d70c216cn%40googlegroups.com.
Re: [sage-release] Re: Sage 9.8 Release Tour
Nice tip! Done also for 9.7, 9.6. On Tuesday, February 14, 2023 at 5:14:50 AM UTC+9 William Stein wrote: Hi, I added py and sh after all the fenced code blocks (triple backticks), so now all the code and shell examples are syntax highlighted. William On Sat, Feb 11, 2023 at 4:58 PM Kwankyu Lee wrote: > > That is a nice summary of the GitHub migration efforts. Thank you. > > -- > You received this message because you are subscribed to the Google Groups "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/fb28801b-4853-4b10-8df9-395ed0fe1f7cn%40googlegroups.com. -- William (http://wstein.org) -- 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/0e7ea138-02de-42d7-8445-19e3b703d16cn%40googlegroups.com.
[sage-release] Re: Sage 9.8 Release Tour
That is a nice summary of the GitHub migration efforts. Thank you. -- 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/fb28801b-4853-4b10-8df9-395ed0fe1f7cn%40googlegroups.com.
[sage-release] Re: Sage 9.8 Release Tour
Thanks. Done. On Saturday, February 11, 2023 at 1:46:33 AM UTC+9 matthia...@gmail.com wrote: The link to it from https://wiki.sagemath.org/ReleaseTours will have to be adjusted after the renames. On Friday, February 10, 2023 at 1:11:18 AM UTC-8 Kwankyu Lee wrote: The release tour for the upcoming 9.8 release is now found at https://github.com/sagemath/sage/wiki/Sage-9.8-Release-Tour -- 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/284187ef-b90c-47d4-8f1d-bb7b2c98d945n%40googlegroups.com.
[sage-release] Sage 9.8 Release Tour
The release tour for the upcoming 9.8 release is now found at https://github.com/sagemath/sage/wiki/Sage-9.8-Release-Tour -- 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/c26a6c31-2391-4364-9ab8-ad863ad0f985n%40googlegroups.com.
[sage-release] Re: Sage 9.8.rc0 released
Please consider #34873 for this release. -- 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/5578ecba-30b3-458c-a759-a64ccd27454fn%40googlegroups.com.
[sage-release] Sage 9.8 Release Tour
It's time to work on the release tour for the upcoming 9.8 release https://trac.sagemath.org/wiki/ReleaseTours/sage-9.8 -- 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/84577afe-b2d2-4064-9909-3f0f7310b1c1n%40googlegroups.com.
Re: [sage-release] Sage 9.8.beta3 released
> However, I don’t understand the difference between the list of features to > be detected (indicated before running the tests) and the list of detected > features (indicated after doctesting). > A feature is not detected until a doctest that requires the feature is encountered (if I remember correctly). -- 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/e1a830f9-6a91-46b3-9718-807124a18ff1n%40googlegroups.com.
Re: [sage-release] Sage 9.8.beta0 released
On Wednesday, September 28, 2022 at 5:45:47 PM UTC+9 Clemens Heuberger wrote: > I encountered one doctest error in > src/sage/schemes/toric/sheaf/klyachko.py > which depends on the random seed: > > Failing seed: 76370439031557170215448337120651728168 This is being tracked in https://trac.sagemath.org/ticket/32773 -- 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/5064bbb5-9f02-4cd0-a043-ae284023a25dn%40googlegroups.com.
[sage-release] Re: Sage 9.7 released
On Tuesday, September 20, 2022 at 11:25:43 PM UTC+9 emanuel.c...@gmail.com wrote: > Upgrade from a detached head 9.7.rc1 to 9.7 successful : passes ptestlong > wit "All tests passed !". You are fortunate. I constantly have sage -t --random-seed=174323800149221866205482120593739177259 src/sage/game_theory/normal_form_game.py # 2 doctests failed sage -t --random-seed=174323800149221866205482120593739177259 src/sage/game_theory/catalog_normal_form_games.py # 15 doctests failed and sage 9.7 is not different. The failed doctests require the optional package "lrslib" installed. So these doctests need "optional - lrslib" tag. Is it right that you installed the optional package? Then I will open a ticket for this. -- 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/188589c5-d80b-4eed-8702-f42431256c7bn%40googlegroups.com.
Re: [sage-release] Sage 9.7.rc2 released
Fixed in #34557 https://trac.sagemath.org/ticket/34557 which needs review. On Monday, September 19, 2022 at 5:38:59 PM UTC+9 Clemens Heuberger wrote: > On most of my machines, ptestlong passes (except for the usual transient > failures in src/sage/interfaces/process.pyx ). > > However, on one machine, where there has not been any problem with > 9.7.rc1, I > consistently get the doctest failure below. It seems to depend on the > random > seed; with another seed (270396188935382102109749143081031101710), the > doctest > passes. > > > > $ ./sage -t --long --warn-long 162.9 > --random-seed=106591066711905509746265618740333072762 > src/sage/rings/polynomial/polynomial_element.pyx > Running doctests with ID 2022-09-19-10-22-38-e10a920f. > Running with SAGE_LOCAL='/local/cheuberg/local/sage-9.7.rc2/local' and > SAGE_VENV='/local/cheuberg/local/sage-9.7.rc2/local/var/lib/sage/venv-python3.10.5' > > > Using --optional=ccache,debian,pip,sage,sage_spkg > Features to be detected: > 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib > > > Doctesting 1 file. > sage -t --long --warn-long 162.9 > --random-seed=106591066711905509746265618740333072762 > src/sage/rings/polynomial/polynomial_element.pyx > ** > File "src/sage/rings/polynomial/polynomial_element.pyx", line 11653, in > sage.rings.polynomial.polynomial_element.Polynomial_generic_dense.quo_rem > Failed example: > f.quo_rem(g) > Expected: > Traceback (most recent call last): > ... > ArithmeticError: division non exact (consider coercing to polynomials over > the fraction field) > Got: > (-7*y^5 + 1/4*y^2 + (-1/2*x + 1/2)*y, > 11/2*y^4 + (-x^2 - 1/3*x + 2/3)*y^3 - 1/3*y^2 - y - 1) > ** > 1 item had failures: > 1 of 24 in > sage.rings.polynomial.polynomial_element.Polynomial_generic_dense.quo_rem > [2716 tests, 1 failure, 8.97 s] > -- > sage -t --long --warn-long 162.9 > --random-seed=106591066711905509746265618740333072762 > src/sage/rings/polynomial/polynomial_element.pyx # 1 doctest failed > -- > Total time for all tests: 19.3 seconds > cpu time: 8.8 seconds > cumulative wall time: 9.0 seconds > Features detected for doctesting: > pytest is not installed in the venv, skip checking tests that rely on it > > > Am 17.09.22 um 13:04 schrieb Volker Braun: > > As always, you can get the latest beta version from the "develop" git > branch. > > Alternatively, the self-contained source tarball is at > > http://www.sagemath.org/download-latest.html > > > > This should be the last rc... > > > > 59ac11a9375 (tag: 9.7.rc2, trac/develop) Updated SageMath version to > 9.7.rc2 > > 4f225f4cc66 (origin/develop) Trac #34533: OS X 12.6 "chained fixups" > warning > > e421c55fafd Trac #34506: Override the arbitrary limit on number of > digits > > printed (Python 3.10.7) > > 08202bc1ba7 (tag: 9.7.rc1) Updated SageMath version to 9.7.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/abfb8851-3171-43d7-999b-91cd3d06852en%40googlegroups.com.
Re: [sage-release] Sage 9.7.rc2 released
This is fixed in #34467, https://trac.sagemath.org/ticket/34467, which is critical. On Sunday, September 18, 2022 at 6:03:12 AM UTC+9 list...@gmail.com wrote: > > The second one appears almost all the time (and always when run alone), > but I have been unable to find a pattern of failure: > sage -t --long --warn-long 53.9 > --random-seed=146248335736799747497433642776404209316 > src/sage/schemes/elliptic_curves/hom_velusqrt.py > ** > File "src/sage/schemes/elliptic_curves/hom_velusqrt.py", line 829, in > sage.schemes.elliptic_curves.hom_velusqrt.EllipticCurveHom_velusqrt > Failed example: > any(map(check, psi.codomain().isomorphisms(phi.codomain( > Expected: > True > Got: > False > ** > 1 item had failures: >1 of 32 in > sage.schemes.elliptic_curves.hom_velusqrt.EllipticCurveHom_velusqrt > [269 tests, 1 failure, 1.29 s] > -- > sage -t --long --warn-long 53.9 > --random-seed=146248335736799747497433642776404209316 > src/sage/schemes/elliptic_curves/hom_velusqrt.py # 1 doctest failed > -- > -- 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/233b2da0-621b-41a8-b1ae-97604bf172b0n%40googlegroups.com.
[sage-release] Re: Sage 9.7.rc1 released
Great! Thanks. On Thursday, September 8, 2022 at 8:39:00 AM UTC+9 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 > > 08202bc1ba7 (HEAD -> develop, trac/develop, tag: 9.7.rc1) Updated SageMath > version to 9.7.rc1 > 2e5af062ddd Trac #33833: Make furo sage standard doc theme > 97dacf88f3c Trac #34450: Standard wheel packages > b37ed1cf0cc Trac #34152: Remove remaining dependencies of bootstrap on > gettext (AC_LIB_RPATH etc.) > cae9ee5177a (tag: 9.7.rc0) Updated SageMath version to 9.7.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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/f79bf0c0-fd36-40e9-9de0-1202f4491499n%40googlegroups.com.
[sage-release] Sage 9.7 release tour
We post the link again here for visibility and easy access: https://trac.sagemath.org/wiki/ReleaseTours/sage-9.7 -- 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/4d755482-2687-4c23-935b-77bd51a7d727n%40googlegroups.com.
[sage-release] Re: Sage 9.7.beta8 released
./bootstrap ? On Wednesday, August 10, 2022 at 5:22:28 PM UTC+9 emanuel.c...@gmail.com wrote: > When trying to upgrade from (vanilla) 9.7.beta6 running on Debian testing > : > > harpent@zen-book-flip:/usr/local/sage-9$ ./configure --help | grep edit > --enable-editable use an editable install of the Sage library > charpent@zen-book-flip:/usr/local/sage-9$ ./configure > --enable-download-from-upstream-url --enable-editable use an editable > install of the Sage library > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > configure: WARNING: you should use --build, --host, --target > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a race-free mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make -j8 sets $(MAKE)... yes > checking whether make -j8 supports nested variables... yes > checking whether to enable maintainer-specific portions of Makefiles... yes > checking whether make -j8 supports the include directive... yes (GNU style) > checking for use-gcc... no > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether the compiler supports GNU C... yes > checking whether gcc accepts -g... yes > checking for gcc option to enable C11 features... none needed > checking whether gcc understands -c and -o together... yes > checking dependency style of gcc... none > checking build system type... Invalid configuration `use': machine > `use-unknown' not recognized > configure: error: /bin/bash ./config/config.sub use failed > > WTF ? > > > Hints ? > > Le lundi 8 août 2022 à 01:14:17 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 >> >> Its probably time to do a release soon-ish, so if there is anything you >> want merged then you should review it asap >> >> 12be2d94c8 (trac/develop, tag: 9.7.beta8) Updated SageMath version to >> 9.7.beta8 >> a3be810660 Trac #10980: Make sure symbolic gridline values are okay >> b860a830e0 Trac #34253: Add discrete logarithm for anomalous elliptic >> curves >> 02b31ccdb1 Trac #34170: Fix docstring markup in sage/coding >> 1da7752fff Trac #34284: hardcode that curves have dimension 1 >> fe346756fe Trac #34002: Sirocco and projective curves >> 4cd8fa6151 Trac #30484: Document using Sage on Windows via Visual Studio >> Code with WSL remote >> c96e796278 Trac #34274: Add sirocco distro info for Conda and Fedora >> cd8f29485f Trac #34267: Add a Home link to the doc root >> e25278cb5a Trac #34265: Make index page single column >> f753c6d701 Trac #34262: Remove toc warnings >> a13aee6a12 Trac #34171: Fix docstring markup in sage/combinat >> 79fbd5ba4f Trac #33870: Dummy package _sagemath: record downstream >> package of Sage in distributions >> 53f49af120 Trac #34264: Standardize jeu de taquin in tableaux >> documentation >> e641d491c5 Trac #34263: Add missing conda.txt for some packages >> 1bfe420613 Trac #34237: Upgrade cython to 0.29.32 >> de447ff5f3 Trac #34217: sage.combinat.finite_state_machine: Remove use of >> "var" >> 6cf6a8efd7 Trac #34167: Fix docstring markup in sage/matroids, >> sage/geometry, sage/modules >> b66cf165f6 Trac #33836: Bug in Lie algebra's chevalley_eilenberg_complex >> method >> 855db5865d Trac #32181: RealSet: Faster operations by scan-line (merging) >> techniques >> 74eaa6fff7 Trac #34249: Fix documentation regarding number of edges of >> Turan graphs >> df6ab59d6f Trac #34084: Fix bug with comparison to 1 in >> IndexedFreeModuleElement >> cad2347c46 Trac #34258: sage_build_cython: Remove normalization of >> -std=c++... flags >> c9fefb1b23 Trac #34244: Don't mark a polynomial doctest "untested" >> ffe67f9e9a Trac #34240: With dot2tex installed, doctesting >> thematic_tutorials/algebraic_combinatorics/rsk.rst opens an image viewer >> 58eb7cbc6a Trac #34226: Allow effective resistance method to work on >> graphs with multiple components >> 6732163e15 Trac #34215: Removing remaining uses of >> is_CallableSymbolicExpression >> 82b3038c13 Trac #34193: configure: Make display of package versions less >> confusing >> 6b0c3ffa67 Trac #34175: `global_height` for polynomials fails when passed >> the zero polynomial >> 2e34fbd740 Trac #34072: pycodestyle
[sage-release] Re: Sage 9.7.beta7 released
It would make a sense to release sage beta8 quickly that just contains https://trac.sagemath.org/ticket/34252 so that developers can make use of the revived Build Documentation badge in trac. -- 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/44cc2b57-6710-4efd-b73f-894c8f313ebfn%40googlegroups.com.
Re: [sage-release] Sage 9.7.beta5 released
On Monday, July 11, 2022 at 2:53:36 PM UTC+9 tdumont wrote: > When upgrading from beta 4 to beta5, I got the following error, which > persists after doing: make doc-clean doc-uninstall; make > > (Unbuntu 22-04, up to date). > > I got this error massage: > [sagemath_doc_html-none] [misc ] WARNING: autodoc: failed to import > module 'sagedoc_conf' from module 'sage.misc'; the following exception > was raised: > [sagemath_doc_html-none] [misc ] No module named > 'sage.misc.sagedoc_conf' > > but I'm not sure this is at the origin of the problem. It seems this is related with 9879ff4e0c Trac #33936: Remove runtime dependency on sage_docbuild introduced in #33763 Really, there should be the file src/sage/misc/sagedoc_conf.py. The message above says it is not there. Check it out. I had no problem in upgrading from beta3 to beta5. -- 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/1d78c6c2-703c-465f-9ea0-6994f8ec9637n%40googlegroups.com.
[sage-release] Re: Sage 9.5.rc0 released
On Wednesday, January 12, 2022 at 11:56:52 AM UTC+9 dmo...@deductivepress.ca wrote: > I installed this version of python yesterday, by downloading a MacOS > installer from https://www.python.org/downloads/macos/. I did this > because my first failed attempt to build 9.5.rc0 was with Python 3.7, and I > thought that having an old python version might be the problem (and I > understand that Python 3.10 is not yet fully supported). I got the same > error message with the old install of python as with this new one. > In my case, it helped to remove the python from www.python.org, and only have python 3.9 installed by homebrew. -- 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/39b9a359-1bed-4e56-b64d-749a2d80f4c4n%40googlegroups.com.
[sage-release] Re: Sage 9.5.rc0 released
> Finally, I would suggest to make sure that the Xcode Command Line > Tools are up to date (using softwareupdate) > In my case, usual "xcode-select --install" and software update reported that the command line tools was up to date, but sage make still failed. I finally succeeded after having installed the latest command line tools downloaded from the apple developer site. -- 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/8ca80f41-970b-47c4-863f-3fe7e3e500b7n%40googlegroups.com.
Re: [sage-release] Re: Sage 9.4.beta0 released
With this release, the command sage -docbuild all pdf stops with the failure below. How about others? Building it/a_tour_of_sage. [a_tour_of] building [latex]: all documents [a_tour_of] Merging environment/index files... [a_tour_of] ... done (0 todos, 1 index, 0 citations, 0 modules) ... (/usr/local/texlive/2021/texmf-dist/tex/latex/hyperref/nameref.sty (/usr/local/texlive/2021/texmf-dist/tex/latex/refcount/refcount.sty) (/usr/local/texlive/2021/texmf-dist/tex/generic/gettitlestring/gettitlestring.s ty)) (/usr/local/texlive/2021/texmf-dist/tex/latex/psnfss/t1phv.fd) *! Package inputenc Error: Unicode character リ (U+30EA)* *(inputenc)not set up for use with LaTeX.* See the inputenc package documentation for explanation. Type H for immediate help. ... l.304 \sphinxmaketitle ? ! Emergency stop. ... l.304 \sphinxmaketitle ! ==> Fatal error occurred, no output PDF file produced! Transcript written on a_tour_of_sage.log. Latexmk: Examining 'a_tour_of_sage.log' === TeX engine is 'pdfTeX' Latexmk: Index file 'a_tour_of_sage.idx' was written Latexmk: Summary of warnings from last run of *latex: =Latex reported missing or unavailable character(s). =See log file for details. Latexmk: Errors, so I did not complete making targets ... -- 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/ac00a487-f51b-41a5-a1ea-e0f28c073a18n%40googlegroups.com.
[sage-release] Re: Sage 9.4.beta0 released
Thanks for the beta release. It seems unusual that the tickets included in the release are not yet closed in Trac. -- 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/5744ef0e-efad-4674-9b56-a6fde44d7aacn%40googlegroups.com.
[sage-release] Re: Sage 9.3 released
It is the greatest release of Sage ever. Thank you! -- 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/9d0775ef-b913-41b1-9617-7b5fdb5dd19dn%40googlegroups.com.
[sage-release] Re: Sage 9.3.rc2 released
Thanks for the release. Incremental build from 9.3.rc1 on mac pro with Big Sur succeeded with no problem. All doctests passed. On Wednesday, April 7, 2021 at 7:33:00 AM UTC+9 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 > > > 824f9cccaf (tag: 9.3.rc2, trac/develop) Updated SageMath version to 9.3.rc2 > 4275b275a2 Trac #31530: New subs bug caused by #30378 > 70711cf13d Trac #31502: GH Actions: Free more disk space > f38d467ae0 Trac #31584: Fix suitesparse/cvxopt /usr/local leakage > 22a11999f2 Trac #31552: Update singular to stop /usr/local from leaking > into Singular build > 24d1bdb786 Trac #31523: Fix dependencies of ipywidgets > ad70e647c5 Trac #31409: Make it possible to disable build of r, rpy2 using > ./configure --disable-r > 7b44d1cb00 Trac #30888: Make $SAGE_LOCAL/bin/sage work again from any > directory, in an environment without SAGE_* variables, following symlinks > 8736c424b9 Trac #31538: i386: openssl and tachyon attempt 64-bit build and > fail > c7c058bd65 Trac #31395: RuntimeError: can't start new thread (due to > memlimit) > 9a1e3ccb6b Trac #31558: homomorphism of extension fields do not preserve > canonical embeddings of the base > 0606dc72e3 Trac #31551: Incorrect conversion from ℚ[-i] to SR > 71123d8021 Trac #30319: Upgrade cddlib to fix wrong intersection of > polytopes > 3da0a29d9f Trac #31536: Fix Sage rich output problems by coupling MathJax > with html > a89f81d778 (tag: 9.3.rc1) Updated SageMath version to 9.3.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/92c3dc06-3a5b-456a-a708-b0ed442634a0n%40googlegroups.com.
[sage-release] Re: Sage 9.2.beta11 released
> > Looks like the command line tools might actually be Xcode 12 beta. This is >> not supported yet -- see https://trac.sagemath.org/ticket/30494 (which >> needs help) >> > Solved by downgrading to Xcode 11.5. Thank you! -- 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/e5ff5c7e-4e1f-48ff-9284-8333090a1ebfn%40googlegroups.com.
[sage-release] Re: Sage 9.2.beta11 released
Hi, I am failing to build from scratch Sage 9.2 beta11 since beta10 or perhaps even earlier beta. My system is macOS 10.15.6 with Xcode 11.7. The log follows: ... ... [gf2x-1.3.0] /Users/kwankyu/GitHub/sage/build/bin/sage-spkg: line 73: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8): No such file or directory [gf2x-1.3.0] Found local metadata for gf2x-1.3.0 [gf2x-1.3.0] Using cached file /Users/kwankyu/GitHub/sage/upstream/gf2x-1.3.0.tar.gz [gf2x-1.3.0] gf2x-1.3.0 [gf2x-1.3.0] [gf2x-1.3.0] Setting up build directory for gf2x-1.3.0 [gf2x-1.3.0] Finished extraction [gf2x-1.3.0] bash: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8): No such file or directory [gf2x-1.3.0] Applying patches from ../patches... [gf2x-1.3.0] Applying ../patches/0001-src-tunetoom.c-delete-duplicate-definition-of-rp.patch [gf2x-1.3.0] patching file src/tunetoom.c [gf2x-1.3.0] [gf2x-1.3.0] Host system: [gf2x-1.3.0] Darwin Hera.local 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_64 [gf2x-1.3.0] [gf2x-1.3.0] C compiler: gcc [gf2x-1.3.0] C compiler version: [gf2x-1.3.0] Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/c++/4.2.1 [gf2x-1.3.0] Apple clang version 12.0.0 (clang-1200.0.31.1) [gf2x-1.3.0] Target: x86_64-apple-darwin19.6.0 [gf2x-1.3.0] Thread model: posix [gf2x-1.3.0] InstalledDir: /Library/Developer/CommandLineTools/usr/bin [gf2x-1.3.0] [gf2x-1.3.0] Package 'gf2x' is currently not installed [gf2x-1.3.0] No legacy uninstaller found for 'gf2x'; nothing to do [gf2x-1.3.0] bash: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8): No such file or directory [gf2x-1.3.0] Deleting old gf2x files. [gf2x-1.3.0] Configuring gf2x-1.3.0 [gf2x-1.3.0] checking build system type... x86_64-apple-darwin19.6.0 [gf2x-1.3.0] checking host system type... x86_64-apple-darwin19.6.0 [gf2x-1.3.0] checking target system type... x86_64-apple-darwin19.6.0 [gf2x-1.3.0] checking for gcc... gcc [gf2x-1.3.0] checking whether the C compiler works... yes [gf2x-1.3.0] checking for C compiler default output file name... a.out [gf2x-1.3.0] checking for suffix of executables... [gf2x-1.3.0] checking whether we are cross compiling... no [gf2x-1.3.0] checking for suffix of object files... o [gf2x-1.3.0] checking whether we are using the GNU C compiler... yes [gf2x-1.3.0] checking whether gcc accepts -g... yes [gf2x-1.3.0] checking for gcc option to accept ISO C89... none needed [gf2x-1.3.0] checking whether gcc understands -c and -o together... rm: conftest.dSYM: is a directory [gf2x-1.3.0] yes [gf2x-1.3.0] checking how to run the C preprocessor... gcc -E [gf2x-1.3.0] checking for grep that handles long lines and -e... /usr/bin/grep [gf2x-1.3.0] checking for egrep... /usr/bin/grep -E [gf2x-1.3.0] checking for ANSI C header files... rm: conftest.dSYM: is a directory [gf2x-1.3.0] rm: conftest.dSYM: is a directory [gf2x-1.3.0] yes [gf2x-1.3.0] checking for sys/types.h... yes [gf2x-1.3.0] checking for sys/stat.h... yes [gf2x-1.3.0] checking for stdlib.h... yes [gf2x-1.3.0] checking for string.h... yes [gf2x-1.3.0] checking for memory.h... yes [gf2x-1.3.0] checking for strings.h... yes [gf2x-1.3.0] checking for inttypes.h... yes [gf2x-1.3.0] checking for stdint.h... yes [gf2x-1.3.0] checking for unistd.h... yes [gf2x-1.3.0] checking for size_t... yes [gf2x-1.3.0] checking for working alloca.h... yes [gf2x-1.3.0] checking for alloca... yes [gf2x-1.3.0] checking for a BSD-compatible install... /usr/bin/install -c [gf2x-1.3.0] checking whether build environment is sane... yes [gf2x-1.3.0] checking for a thread-safe mkdir -p... config/install-sh -c -d [gf2x-1.3.0] checking for gawk... no [gf2x-1.3.0] checking for mawk... no [gf2x-1.3.0] checking for nawk... no [gf2x-1.3.0] checking for awk... awk [gf2x-1.3.0] checking whether make sets $(MAKE)... yes [gf2x-1.3.0] checking whether make supports the include directive... yes (GNU style) [gf2x-1.3.0] checking whether make supports nested variables... yes [gf2x-1.3.0] checking dependency style of gcc... none [gf2x-1.3.0] checking whether to enable maintainer-specific portions of Makefiles... no [gf2x-1.3.0] checking how to print strings... printf [gf2x-1.3.0] checking for a sed that does not truncate output... /usr/bin/sed [gf2x-1.3.0] checking for fgrep... /usr/bin/grep -F [gf2x-1.3.0] checking for ld used by gcc... /Library/Developer/CommandLineTools/usr/bin/ld [gf2x-1.3.0] checking if the linker (/Library/Developer/CommandLineTools/usr/bin/ld) is GNU ld... no [gf2x-1.3.0] checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B [gf2x-1.3.0] checking the name
[sage-release] Re: Sage 9.0 released
Wow! I would take the honour to be the second person to celebrate the release of Sage on Python 3 by default. I thank the great people in the Sage developer community who made this! A nice present for the new year! -- 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/52508a17-2e9c-4766-a722-1045a711f415%40googlegroups.com.
[sage-release] Re: Sage 8.8.rc0 released
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.
Re: [sage-release] Re: Sage 8.4.beta7 released
On Wednesday, October 3, 2018 at 10:01:40 PM UTC+9, Samuel Lelievre wrote: > > Wed 2018-10-03 12:36 UTC+2, Travis Scrimshaw: > > > > On Wednesday, October 3, 2018 at 7:35:08 PM UTC+10, Kwankyu Lee wrote: > >> > >> On Wednesday, October 3, 2018 at 3:14:32 PM UTC+9, Travis Scrimshaw > wrote: > >>> > >>> I believe there is a Heisenbug in > src/sage/rings/function_field/ideal.py. > > >>> Here is a specific test that can sometimes fail: > >>> > >>> sage: K. = FunctionField(GF(3^2)); R. = K[] > >>> sage: F. = K.extension(t^3 + t^2 - x^4) > >>> sage: Oinf = F.maximal_order_infinite() > >>> sage: I = Oinf.ideal(1/y) > >>> sage: I.factor() # This will sometimes fail > >>> > >>> I suspect people without meataxe will not have this failure. > > Is this file added by some optional package, such as meataxe? > > Without meataxe, the directory src/sage/rings/function_field > has a file function_field_ideal.py but no file ideal.py --- and > > sage: Oinf = F.maximal_order_infinite() > > gives a NotImplementedError. > > > I created https://trac.sagemath.org/ticket/26389 > > (Simon, I have cc-ed you). > > Note that the ticket summary has "Hisenbug" for "Heisenbug" > and it might make sense to start the ticket description with > an indication that this happens with Meataxe installed. > This is on Sage 8.4.beta 7. -- 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.
[sage-release] Re: Sage 8.4.beta7 released
On Wednesday, October 3, 2018 at 3:14:32 PM UTC+9, tsc...@ucdavis.edu wrote: > > I believe there is a Heisenbug in src/sage/rings/function_field/ideal.py. > Here is a specific test that can sometimes fail: > > sage: K. = FunctionField(GF(3^2)); R. = K[] > sage: F. = K.extension(t^3 + t^2 - x^4) > sage: Oinf = F.maximal_order_infinite() > sage: I = Oinf.ideal(1/y) > sage: I.factor() # This will sometimes fail > --- > TypeError Traceback (most recent call last > ) > > I suspect people without meataxe will not have this failure. > Perhaps true. I must be the person who ran this test most number of times and I never encountered this failure. -- 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.1.rc0 released
I noticed this:
$ sage -t src/sage/rings/finite_rings/*
Running doctests with ID 2017-11-17-23-04-49-f065787a.
Git branch: finite_field_extension_trac24195_dev
Using --optional=mpir,python2,sage
Traceback (most recent call last):
File "/Users/Kwankyu/GitHub/sage/src/bin/sage-runtests", line 125, in
err = DC.run()
File
"/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
line 1141, in run
self.expand_files_into_sources()
File
"/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/control.py",
line 751, in expand_files_into_sources
self.sources = [FileDocTestSource(path, self.options) for path in
expand()]
File
"/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/sources.py",
line 525, in __init__
raise ValueError("unknown file extension %r"%ext)
ValueError: unknown file extension '.h'
$
The problematic file is
$ ls -l src/sage/rings/finite_rings/*.h
-rw-r--r-- 1 Kwankyu staff 311 Nov 17 10:13
src/sage/rings/finite_rings/integer_mod_limits.h
$
Is this normal situation? This betrays my belief that a command like
$ sage -t src/sage/rings/finite_rings/*
always works fine.
--
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.1.rc0 released
On Friday, November 17, 2017 at 6:53:41 PM UTC+9, Thierry wrote: > > > How much available RAM do you have ? Building the documentation is no > longer the last step, hence if that fails, everything after that is not > built. Ah, I didn't know that. This (building the documentation is no longer the last step) sounds a big change to me. I wonder when that change was made. > If you do not have enough RAM to build the doc, you can compile the > rest of Sage with: > > make build It is Mac Pro with 32GB RAM. I never suspected that the Sage build on the machine could fail because of not enough RAM. Ok. Thank you guys for enlightening me :-) Kwankyu -- 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.1.rc0 released
On Thursday, November 16, 2017 at 8:38:52 PM UTC+9, Jeroen Demeyer wrote: > > > It seems that sympy simply wasn't built. I am not aware of any bug in > the build system (especially not specific to OS X) which could cause that. > The fresh build (of actually Sage 8.1rc1) finished with no problem. Also the strange behaviour reported above does not appear with the fresh Sage. Perhaps my previous Sage installation was somehow corrupted. I don't know why... Sorry for the noise. Thank you! -- 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.1.rc0 released
> > Sorry to ask a silly question, but are you sure that > > (1) You actually ran "make" > Yes. But this was not a fresh one. I ran "make distclean", and then "make". > (2) That run of "make" succeeded without errors > There was an error in building doc. I ignored this as there was no problem in running Sage. > It seems that sympy simply wasn't built. I am not aware of any bug in > the build system (especially not specific to OS X) which could cause that. > Ok. Then I will try a fresh build from source, and report the result. Thank you for your attention. -- 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.1.rc0 released
Then I created a new directory at SAGE_ROOT/src/ext/directory and put a file "test.txt" $ ls -l src/ext/ total 0 drwxr-xr-x 3 Kwankyu staff 102 Nov 16 15:42 directory drwxr-xr-x 4 Kwankyu staff 136 Apr 15 2015 doctest drwxr-xr-x 5 Kwankyu staff 170 Apr 14 2016 gap drwxr-xr-x 3 Kwankyu staff 102 Mar 4 2016 graphs drwxr-xr-x 7 Kwankyu staff 238 Jun 11 2015 images drwxr-xr-x 7 Kwankyu staff 238 Jul 26 23:26 kenzo drwxr-xr-x 5 Kwankyu staff 170 Jun 11 2015 magma drwxr-xr-x 3 Kwankyu staff 102 Jun 11 2015 mwrank drwxr-xr-x 4 Kwankyu staff 136 Jun 11 2015 notebook-ipython drwxr-xr-x 5 Kwankyu staff 170 Apr 15 2015 pari drwxr-xr-x 3 Kwankyu staff 102 Jun 11 2015 pickle_jar drwxr-xr-x 3 Kwankyu staff 102 Jul 26 23:26 threejs drwxr-xr-x 5 Kwankyu staff 170 Apr 13 2016 valgrind $ and then I ran $ sage -br and I expected the new directory "directory" is created at "local/share/sage/ext/", but I get: $ ls -l local/share/sage/ext/ total 0 drwxr-xr-x 4 Kwankyu staff 136 Nov 15 19:19 doctest drwxr-xr-x 5 Kwankyu staff 170 Nov 15 19:19 gap drwxr-xr-x 3 Kwankyu staff 102 Nov 15 19:19 graphs drwxr-xr-x 7 Kwankyu staff 238 Nov 15 19:19 images drwxr-xr-x 7 Kwankyu staff 238 Nov 15 19:19 kenzo drwxr-xr-x 5 Kwankyu staff 170 Nov 15 19:19 magma drwxr-xr-x 3 Kwankyu staff 102 Nov 15 19:19 mwrank drwxr-xr-x 4 Kwankyu staff 136 Nov 15 19:19 notebook-ipython drwxr-xr-x 5 Kwankyu staff 170 Nov 15 19:19 pari drwxr-xr-x 3 Kwankyu staff 102 Nov 15 19:19 pickle_jar drwxr-xr-x 3 Kwankyu staff 102 Nov 15 19:19 threejs drwxr-xr-x 7 Kwankyu staff 238 Nov 15 19:19 valgrind $ According to the developer guide, Non-Python Sage source code and supporting files should be placed in appropriate subdirectories of SAGE_ROOT/src/ext/. They will then be automatically copied to the corresponding subdirectories of SAGE_ROOT/local/share/sage/ext/ during the build process and can be accessed at runtime using SAGE_EXTCODE. -- 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.1.rc0 released
So I ran sage -i sympy and Sage installed sympy. Then now this works fine. $ sage -t src/sage/rings/function_field/* -- 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.1.rc0 released
I get the following just after "make", Hera:sage$ sage -t src/sage/rings/function_field/* Running doctests with ID 2017-11-16-15-36-55-9cd5f354. Git branch: develop Using --optional=mpir,python2,sage Doctesting 8 files. Traceback (most recent call last): File "/Users/Kwankyu/GitHub/sage/src/bin/sage-runtests", line 125, in err = DC.run() File "/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1144, in run self.run_doctests() File "/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/control.py", line 867, in run_doctests self.dispatcher = DocTestDispatcher(self) File "/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 1403, in __init__ init_sage() File "/Users/Kwankyu/GitHub/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 134, in init_sage from sympy.printing.pretty.stringpict import stringPict ImportError: No module named sympy.printing.pretty.stringpict Hera: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 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.
[sage-release] Re: Sage 8.1.rc0 released
Hi, Does this release support Xcode 9.1 on mac? I built this release with Xcode 9.1, and the Sage built shows strange behaviors. Is this because of Xcode 9.1? -- 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.
[sage-release] Re: Sage 8.1.beta2 released
Indeed. sage -t --long --warn-long 75.4 src/sage/rings/function_field/function_field .py ** File "src/sage/rings/function_field/function_field.py", line 69, in sage. rings.function_field.function_field Warning, slow doctest: TestSuite(M).run() # long time (52s on sage.math, 2012) Test ran for 194.71 s [457 tests, 251.53 s] -- All tests passed! -- Total time for all tests: 251.7 seconds cpu time: 249.2 seconds cumulative wall time: 251.5 seconds No doctest should take more than 30 seconds, according to the developer guide. Hence these long tests should be deleted. -- 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.
[sage-release] Re: Sage 7.5.beta5 released
I just noticed sage$: sage -t src/sage/rings/function_field/* ... ValueError: unknown file extension '.pyc' This worked fine previously... -- 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.
