[sage-release] Re: Sage 9.7.beta5 released
I've opened https://trac.sagemath.org/ticket/34181 for this. On Thursday, July 14, 2022 at 7:36:15 AM UTC-7 Matthias Köppe wrote: > On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote: > >> When I did an incremental build with the venv-python3.10.3 in place, a >> new venv named python3.10.5 was created. But that new venv depends on the >> old 3.10.3 venv. In fact, there are at least 16 executable files in >> sage/venv-python3.10.5/bin for which the shebang points to >> sage/venv-python3.10.3/bin/python3 >> This prevents sage from working after the 3.10.3 venv is removed. >> > > >> I am guessing that these bad shebangs are created because the old venv is >> actually being used to build the new venv. >> > > No, I don't think that's what's happening. > > It's probably just that the scripts are cached in > pkgs/sagemath-standard/build/scripts/ > > Try "make sagelib-clean". > > > > -- 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/de5fae15-f7c3-45f7-8a0f-b0c3e7491b75n%40googlegroups.com.
[sage-release] Re: Sage 9.7.beta5 released
On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote: > If I delete all of the venvs before starting an incremental build will the > build still work, and will it create a new venv that is appropriate for its > python, even if the python version has not changed? > Yes. -- 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/33b5a586-19a6-4d80-93d8-3189a182a3ccn%40googlegroups.com.
[sage-release] Re: Sage 9.7.beta5 released
On Thursday, July 14, 2022 at 5:30:47 AM UTC-7 marc@gmail.com wrote: > When I did an incremental build with the venv-python3.10.3 in place, a new > venv named python3.10.5 was created. But that new venv depends on the old > 3.10.3 venv. In fact, there are at least 16 executable files in > sage/venv-python3.10.5/bin for which the shebang points to > sage/venv-python3.10.3/bin/python3 > This prevents sage from working after the 3.10.3 venv is removed. > > I am guessing that these bad shebangs are created because the old venv is > actually being used to build the new venv. > No, I don't think that's what's happening. It's probably just that the scripts are cached in pkgs/sagemath-standard/build/scripts/ Try "make sagelib-clean". -- 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/8960ed12-d6b1-4f3a-a98e-62224c411375n%40googlegroups.com.
[sage-release] Re: Sage 9.7.beta5 released
I used sed to fix the 16 files with bad shebangs in sage/venv-python3.10.5/bin and that appeared to produce a working copy of sage. So perhaps the bad shebangs are the only reason that venv-python3.10.5 depends on venv-python3.10.3. - Marc On Thursday, July 14, 2022 at 7:30:47 AM UTC-5 Marc Culler wrote: > That statement is actually false. I think this issue needs to be > addressed. I think the old venvs should be removed when doing an > incremental build, since I cannot think of any use for them. > > Here is the problem. When I did an incremental build with the > venv-python3.10.3 in place, a new venv named python3.10.5 was created. But > that new venv depends on the old 3.10.3 venv. In fact, there are at least > 16 executable files in sage/venv-python3.10.5/bin for which the shebang > points to > sage/venv-python3.10.3/bin/python3 > This prevents sage from working after the 3.10.3 venv is removed. There > may be other dependencies between the two venvs as well. > > It seems like bad practice to create a venv which depends on another > venv. That defeats the purpose of a venv. Also it does not make sense to > me for incremental builds to cause the sage directory to contain an > ever-expanding set of virtual envs each of which depends on the previous > one. > > I am guessing that these bad shebangs are created because the old venv is > actually being used to build the new venv. > > Here is a list of the files with bad shebangs in sage/venv-python3.10.5/bin > math-readline > sage-cleaner > sage-coverage > sage-cython > sage-eval > sage-fixdoctests > sage-ipython > sage-list-packages > sage-notebook > sage-num-threads.py > sage-preparse > sage-run > sage-run-cython > sage-runtests > sage-startuptime.py > sage-venv-config > > - Marc > > > > > > On Wednesday, July 13, 2022 at 4:55:02 PM UTC-5 matthia...@gmail.com > wrote: > >> Yes, you can delete the old venv. We do not uninstall other venvs that >> may have been built previously. >> >> On Wednesday, July 13, 2022 at 1:08:57 PM UTC-7 marc@gmail.com wrote: >> >>> After working around the issues with the bootstrap script and >>> symengine_py I have managed to build 9.7.beta5 on an arm mac mini. This >>> was an incremental build from beta4. When the build finished I noticed >>> that both sage/local/var/lib/sage/venv-python3.10.3 and >>> sage/local/var/lib/sage/venv-python3.10.5 existed. The 3.10.3 venv cannot >>> be required, because it never gets created if make distclean is run first. >>> So it seems to be doing nothing but wasting disk space. Shouldn't it get >>> removed once the build finishes? >>> >>> - Marc >>> >>> On Sunday, July 10, 2022 at 6:24:36 PM UTC-5 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 625ac58151 (trac/develop, tag: 9.7.beta5) Updated SageMath version to 9.7.beta5 413ff13c54 Trac #34056: cleaning two files in quadratic forms cb65d06dd2 Trac #34055: Remove "ssl" target from Makefile 0740d209ca Trac #34053: pycodestyle cleanup in src/sage/graphs/base/static_sparse_graph.pyx 539a5c073c Trac #34046: pycodestyle cleanup in src/sage/graphs/base/boost_graph.pyx 6790b30aeb Trac #34044: pycodestyle cleanup in src/sage/graphs/generators/smallgraphs.py (part 3) 6e4de5191b Trac #34043: pycodestyle cleanup in src/sage/graphs/generators/smallgraphs.py (part 2) 3d2f91c326 Trac #34042: pycodestyle cleanup in src/sage/graphs/generators/smallgraphs.py (part 1) 45c1d36c3a Trac #34034: pycodestyle cleanup in src/sage/graphs/generators/random.py 9f1388bac5 Trac #34032: pycodestyle cleanup in src/sage/graphs/generators/world_map.py 248a6e15e6 Trac #34023: pycodestyle cleanup in distance_regular.pyx (part 1) 0a77b4496f Trac #34022: pycodestyle cleanup in src/sage/graphs/generators/classical_geometries.py 0cec8684d7 Trac #34135: modernize super() in groups 38b2bf7529 Trac #34058: sage 9.6 special function translation issue with fricas. elliptic_ec 720adde3bb Trac #32716: pkgs/sagemath-*/tox.ini: Create environment that uses Sage's python as the basepython, fix sagemath-standard deps 6294f36ee4 Trac #28925: Modify find_python_sources to support modularization of sagelib by native namespace packages (PEP 420) 5063ca7441 Trac #34021: pycodestyle in 5 files of src/sage/graphs/generators 648ea02cda Trac #34018: pycodestyle cleanup in src/sage/graphs/graph_decompositions/ 44562ec0cf Trac #34016: improve pycodestyle in 4 files in graphs aa79451a04 Trac #34015: pycodestyle cleanup in planarity.pyx and path_enumeration.pyx 3268d19fa5 Trac #34013: pycodestyle cleanup in schnyder.py and print_graphs.py a6f5a56109 Trac #34012: pycodestyle
[sage-release] Re: Sage 9.7.beta5 released
I don't want to have to remember to do this by hand. If I delete all of the venvs before starting an incremental build will the build still work, and will it create a new venv that is appropriate for its python, even if the python version has not changed? - Marc On Wednesday, July 13, 2022 at 4:55:02 PM UTC-5 matthia...@gmail.com wrote: > Yes, you can delete the old venv. We do not uninstall other venvs that may > have been built previously. > > On Wednesday, July 13, 2022 at 1:08:57 PM UTC-7 marc@gmail.com wrote: > >> After working around the issues with the bootstrap script and >> symengine_py I have managed to build 9.7.beta5 on an arm mac mini. This >> was an incremental build from beta4. When the build finished I noticed >> that both sage/local/var/lib/sage/venv-python3.10.3 and >> sage/local/var/lib/sage/venv-python3.10.5 existed. The 3.10.3 venv cannot >> be required, because it never gets created if make distclean is run first. >> So it seems to be doing nothing but wasting disk space. Shouldn't it get >> removed once the build finishes? >> >> - Marc >> >> On Sunday, July 10, 2022 at 6:24:36 PM UTC-5 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 >>> >>> 625ac58151 (trac/develop, tag: 9.7.beta5) Updated SageMath version to >>> 9.7.beta5 >>> 413ff13c54 Trac #34056: cleaning two files in quadratic forms >>> cb65d06dd2 Trac #34055: Remove "ssl" target from Makefile >>> 0740d209ca Trac #34053: pycodestyle cleanup in >>> src/sage/graphs/base/static_sparse_graph.pyx >>> 539a5c073c Trac #34046: pycodestyle cleanup in >>> src/sage/graphs/base/boost_graph.pyx >>> 6790b30aeb Trac #34044: pycodestyle cleanup in >>> src/sage/graphs/generators/smallgraphs.py (part 3) >>> 6e4de5191b Trac #34043: pycodestyle cleanup in >>> src/sage/graphs/generators/smallgraphs.py (part 2) >>> 3d2f91c326 Trac #34042: pycodestyle cleanup in >>> src/sage/graphs/generators/smallgraphs.py (part 1) >>> 45c1d36c3a Trac #34034: pycodestyle cleanup in >>> src/sage/graphs/generators/random.py >>> 9f1388bac5 Trac #34032: pycodestyle cleanup in >>> src/sage/graphs/generators/world_map.py >>> 248a6e15e6 Trac #34023: pycodestyle cleanup in distance_regular.pyx >>> (part 1) >>> 0a77b4496f Trac #34022: pycodestyle cleanup in >>> src/sage/graphs/generators/classical_geometries.py >>> 0cec8684d7 Trac #34135: modernize super() in groups >>> 38b2bf7529 Trac #34058: sage 9.6 special function translation issue with >>> fricas. elliptic_ec >>> 720adde3bb Trac #32716: pkgs/sagemath-*/tox.ini: Create environment that >>> uses Sage's python as the basepython, fix sagemath-standard deps >>> 6294f36ee4 Trac #28925: Modify find_python_sources to support >>> modularization of sagelib by native namespace packages (PEP 420) >>> 5063ca7441 Trac #34021: pycodestyle in 5 files of >>> src/sage/graphs/generators >>> 648ea02cda Trac #34018: pycodestyle cleanup in >>> src/sage/graphs/graph_decompositions/ >>> 44562ec0cf Trac #34016: improve pycodestyle in 4 files in graphs >>> aa79451a04 Trac #34015: pycodestyle cleanup in planarity.pyx and >>> path_enumeration.pyx >>> 3268d19fa5 Trac #34013: pycodestyle cleanup in schnyder.py and >>> print_graphs.py >>> a6f5a56109 Trac #34012: pycodestyle cleanup in >>> sage.graphs.spanning_tree.pyx, weakly_chordal.pyx >>> b5041b18ad Trac #34011: pycodestyle cleanup in sage.graphs.views.pyx, >>> trees.pyx, traversals.pyx >>> 81f843e76b Trac #34010: pycodestyle cleanup in >>> sage.graphs.tutte_polynomial.py >>> c2550f7093 Trac #34009: pycodestyle cleanup in >>> sage.graphs.hyperbolicity.pyx >>> 44a5f5b3d9 Trac #33952: Add methods to compute holomorphic differentials >>> of function field >>> 6ea1dc5f9e Trac #33868: Add modules over integral domain >>> b593b48ed7 Trac #33791: ci-cygwin: Refactor using reusable workflows >>> 1fc79b83f6 Trac #33788: GH Actions: Split ci-macos.yml out from tox.yml >>> 931d6ac039 Trac #33777: Deprecate Sage's CHomP interface >>> c364788de0 Trac #33708: make elliptic-curve isogenies compute Montgomery >>> codomains >>> 64e29cf9d9 Trac #33144: Remove some py2 tags in explain_pickle >>> 1c0f22aabf Trac #34132: Update primesieve to 8.0, primecount to 7.4 >>> 9793520438 <(979)%20352-0438> Trac #34121: Heegner point method can >>> return a point defined over the wrong field >>> 3208d2c51f Trac #34112: some details in L-functions >>> 65722f53c1 Trac #34111: 'PosixPath' object has no attribute >>> '_libgap_init_' >>> d860f2e146 Trac #34098: Installation manual: Improvements for homebrew, >>> conda >>> afb3761f26 Trac #34090: Update python3 to 3.10.5 >>> f56dc7b1f3 Trac #34085: fix some details in braid groups >>> b1a00624dc Trac #34082: Add an option up_to_isomorphism for is_subgraph >>> 8c5d4ca3a4 Trac #34080: pycodestyle cleanup in src/sage/graphs/digraph.py >>> 7ad1358ac7 Trac #34062: enhance
[sage-release] Re: Sage 9.7.beta5 released
That statement is actually false. I think this issue needs to be addressed. I think the old venvs should be removed when doing an incremental build, since I cannot think of any use for them. Here is the problem. When I did an incremental build with the venv-python3.10.3 in place, a new venv named python3.10.5 was created. But that new venv depends on the old 3.10.3 venv. In fact, there are at least 16 executable files in sage/venv-python3.10.5/bin for which the shebang points to sage/venv-python3.10.3/bin/python3 This prevents sage from working after the 3.10.3 venv is removed. There may be other dependencies between the two venvs as well. It seems like bad practice to create a venv which depends on another venv. That defeats the purpose of a venv. Also it does not make sense to me for incremental builds to cause the sage directory to contain an ever-expanding set of virtual envs each of which depends on the previous one. I am guessing that these bad shebangs are created because the old venv is actually being used to build the new venv. Here is a list of the files with bad shebangs in sage/venv-python3.10.5/bin math-readline sage-cleaner sage-coverage sage-cython sage-eval sage-fixdoctests sage-ipython sage-list-packages sage-notebook sage-num-threads.py sage-preparse sage-run sage-run-cython sage-runtests sage-startuptime.py sage-venv-config - Marc On Wednesday, July 13, 2022 at 4:55:02 PM UTC-5 matthia...@gmail.com wrote: > Yes, you can delete the old venv. We do not uninstall other venvs that may > have been built previously. > > On Wednesday, July 13, 2022 at 1:08:57 PM UTC-7 marc@gmail.com wrote: > >> After working around the issues with the bootstrap script and >> symengine_py I have managed to build 9.7.beta5 on an arm mac mini. This >> was an incremental build from beta4. When the build finished I noticed >> that both sage/local/var/lib/sage/venv-python3.10.3 and >> sage/local/var/lib/sage/venv-python3.10.5 existed. The 3.10.3 venv cannot >> be required, because it never gets created if make distclean is run first. >> So it seems to be doing nothing but wasting disk space. Shouldn't it get >> removed once the build finishes? >> >> - Marc >> >> On Sunday, July 10, 2022 at 6:24:36 PM UTC-5 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 >>> >>> 625ac58151 (trac/develop, tag: 9.7.beta5) Updated SageMath version to >>> 9.7.beta5 >>> 413ff13c54 Trac #34056: cleaning two files in quadratic forms >>> cb65d06dd2 Trac #34055: Remove "ssl" target from Makefile >>> 0740d209ca Trac #34053: pycodestyle cleanup in >>> src/sage/graphs/base/static_sparse_graph.pyx >>> 539a5c073c Trac #34046: pycodestyle cleanup in >>> src/sage/graphs/base/boost_graph.pyx >>> 6790b30aeb Trac #34044: pycodestyle cleanup in >>> src/sage/graphs/generators/smallgraphs.py (part 3) >>> 6e4de5191b Trac #34043: pycodestyle cleanup in >>> src/sage/graphs/generators/smallgraphs.py (part 2) >>> 3d2f91c326 Trac #34042: pycodestyle cleanup in >>> src/sage/graphs/generators/smallgraphs.py (part 1) >>> 45c1d36c3a Trac #34034: pycodestyle cleanup in >>> src/sage/graphs/generators/random.py >>> 9f1388bac5 Trac #34032: pycodestyle cleanup in >>> src/sage/graphs/generators/world_map.py >>> 248a6e15e6 Trac #34023: pycodestyle cleanup in distance_regular.pyx >>> (part 1) >>> 0a77b4496f Trac #34022: pycodestyle cleanup in >>> src/sage/graphs/generators/classical_geometries.py >>> 0cec8684d7 Trac #34135: modernize super() in groups >>> 38b2bf7529 Trac #34058: sage 9.6 special function translation issue with >>> fricas. elliptic_ec >>> 720adde3bb Trac #32716: pkgs/sagemath-*/tox.ini: Create environment that >>> uses Sage's python as the basepython, fix sagemath-standard deps >>> 6294f36ee4 Trac #28925: Modify find_python_sources to support >>> modularization of sagelib by native namespace packages (PEP 420) >>> 5063ca7441 Trac #34021: pycodestyle in 5 files of >>> src/sage/graphs/generators >>> 648ea02cda Trac #34018: pycodestyle cleanup in >>> src/sage/graphs/graph_decompositions/ >>> 44562ec0cf Trac #34016: improve pycodestyle in 4 files in graphs >>> aa79451a04 Trac #34015: pycodestyle cleanup in planarity.pyx and >>> path_enumeration.pyx >>> 3268d19fa5 Trac #34013: pycodestyle cleanup in schnyder.py and >>> print_graphs.py >>> a6f5a56109 Trac #34012: pycodestyle cleanup in >>> sage.graphs.spanning_tree.pyx, weakly_chordal.pyx >>> b5041b18ad Trac #34011: pycodestyle cleanup in sage.graphs.views.pyx, >>> trees.pyx, traversals.pyx >>> 81f843e76b Trac #34010: pycodestyle cleanup in >>> sage.graphs.tutte_polynomial.py >>> c2550f7093 Trac #34009: pycodestyle cleanup in >>> sage.graphs.hyperbolicity.pyx >>> 44a5f5b3d9 Trac #33952: Add methods to compute holomorphic differentials >>> of function field >>> 6ea1dc5f9e Trac
