[sage-devel] sage-system-python use in runtime
I'm trying to build sage 9.0.rc1 for conda. For conda what I do is I run, 1. Run configure 2. cp src/bin/* to /bin 3. cp src/ext/* to /share/sage/ext 4. run `python setup.py install` in src This has worked fine until 8.9 In 9.0 some scripts in `src/bin/` use `sage-system-python` which is in `build/bin/`. Shouldn't scripts like `sage-system-python` be used only in scripts under `build`? Isuru -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CA%2B01voPKxZExqVsi6AsbQJ-hejuFQrfN7Rnb9s40DpjKpNxapg%40mail.gmail.com.
[sage-devel] Re: Buiding sage on a Raspberry Pi 4B
For what it's worth, I regularly build and test sage-on-nixos on aarch64. The testsuite shows no issues, except some transient timeouts which may or may not be caused by the architecture. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/14f1223e-e666-472a-bae4-17e549e073dd%40googlegroups.com.
[sage-devel] Re: Buiding sage on a Raspberry Pi 4B
Hi Dima, I don't understand what I see and I hate that. Seeing 4 CPU's producing heat, four instances of python 3 gathering CPU time. producing 0 test of 0.00s duration. There is something not OK in the Raspberry Pi system. I don't trust the memory management system at all. make ptestlong ended: -- sage -t --long --warn-long 253.8 src/sage/rings/tests.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/schemes/elliptic_curves/ell_rational_field.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/rings/function_field/function_field.py # Timed out sage -t --long --warn-long 253.8 src/sage/schemes/cyclic_covers/cycliccover_finite_field.py # Timed out sage -t --long --warn-long 253.8 src/sage/combinat/sf/macdonald.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/combinat/ncsf_qsym/ncsf.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/algebras/lie_algebras/classical_lie_algebra.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/function_field/function_field_valuation.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/number_field/number_field.py # Timed out sage -t --long --warn-long 253.8 src/sage/geometry/cone.py # Timed out sage -t --long --warn-long 253.8 src/sage/modular/btquotients/pautomorphicform.py # Timed out sage -t --long --warn-long 253.8 src/sage/arith/misc.py # Timed out sage -t --long --warn-long 253.8 src/sage/graphs/strongly_regular_db.pyx # Timed out sage -t --long --warn-long 253.8 src/sage/structure/coerce_dict.pyx # 1 doctest failed sage -t --long --warn-long 253.8 src/sage/modular/modform_hecketriangle/abstract_space.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/modular/modform/find_generators.py # Timed out sage -t --long --warn-long 253.8 src/sage/modular/modform/cuspidal_submodule.py # Timed out sage -t --long --warn-long 253.8 src/sage/schemes/toric/chow_group.py # Timed out sage -t --long --warn-long 253.8 src/sage/groups/matrix_gps/finitely_generated.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/function_field/ideal.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/misc/functional.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/number_field/totallyreal_rel.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/modular/hypergeometric_motive.py # Timed out sage -t --long --warn-long 253.8 src/sage/categories/loop_crystals.py # Timed out sage -t --long --warn-long 253.8 src/sage/algebras/iwahori_hecke_algebra.py # Timed out sage -t --long --warn-long 253.8 src/sage/schemes/curves/projective_curve.py # Timed out sage -t --long --warn-long 253.8 src/sage/modular/overconvergent/genus0.py # Timed out sage -t --long --warn-long 253.8 src/sage/combinat/permutation.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/number_field/number_field_ideal.py # Timed out sage -t --long --warn-long 253.8 src/sage/combinat/designs/orthogonal_arrays_find_recursive.pyx # Timed out sage -t --long --warn-long 253.8 src/sage/geometry/triangulation/element.py # Timed out sage -t --long --warn-long 253.8 src/sage/schemes/elliptic_curves/period_lattice.py # Timed out sage -t --long --warn-long 253.8 src/sage/schemes/elliptic_curves/ell_field.py # Timed out sage -t --long --warn-long 253.8 src/sage/modular/arithgroup/congroup_gammaH.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/number_field/galois_group.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/valuation/limit_valuation.py # Timed out sage -t --long --warn-long 253.8 src/sage/combinat/e_one_star.py # Timed out sage -t --long --warn-long 253.8 src/sage/combinat/designs/latin_squares.py # Timed out sage -t --long --warn-long 253.8 src/sage/combinat/designs/evenly_distributed_sets.pyx # Timed out sage -t --long --warn-long 253.8 src/sage/geometry/polyhedron/combinatorial_polyhedron/polyhedron_face_lattice.pyx # Timed out sage -t --long --warn-long 253.8 src/sage/calculus/wester.py # Timed out sage -t --long --warn-long 253.8 src/sage/groups/artin.py # Timed out sage -t --long --warn-long 253.8 src/sage/symbolic/ring.pyx # Timed out sage -t --long --warn-long 253.8 src/sage/structure/coerce.pyx # Timed out sage -t --long --warn-long 253.8 src/sage/modular/modsym/tests.py # Timed out sage -t --long --warn-long 253.8 src/sage/modular/modform/ambient_g1.py # Timed out sage -t --long --warn-long 253.8 src/sage/tests/books/judson-abstract-algebra/fields-sage.py # Timed out sage -t --long --warn-long 253.8 src/sage/rings/polynomial/multi_polynomial_element.py # Killed due to segmentation fault sage -t --long --warn-long 253.8 src/sage/repl/preparse.py # Timed out sage -t --long --warn-long 253.8 src/s
Re: [sage-devel] Adopting orphaned math packages
On 12/20/19 10:57 AM, E. Madison Bray wrote: > > I found .spkg archives (which are essentially just zipfiles, or > tarballs, I forget which, containing the upstream sources along with > some Sage-specific stuff) for 0.3, 0.3.1, and 0.3.2 if you want them. > But perhaps it's not even terribly meaningful if they're *that* old > and we don't have anything between 0.3.2 and 2.0. Up to you. I looked in earnest for a copy of v1.0 and wasn't able to find one. I'm ready to give up and move forward. Can you please set things up on gitlab? The only thing I plan to do immediately is merge the patches that everyone is already carrying, and make a v2.0.1 release. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/912dc705-52db-cece-8943-386b40cfe2c4%40orlitzky.com.
Re: [sage-devel] "pulling" an older branch from the develop tree
On 12/30/19 3:33 PM, 'Justin C. Walker' via sage-devel wrote: > I did not been pay close attention to the details of working with the develop > tree and other repositories, and have a question: > > I would like to be able to clone an earlier sage release than what’s at the > top of the tree. After poking the documentation, I think this would clone > the previous release to the current (rc1) release. Is this correct? > > git clone git://github.com/sagemath/sage.git 9.0-rc0 > > Thanks! And apologies for lame questions… > Just clone normally, and then "git checkout" the thing that you want. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/dfb215e9-7c0f-5201-c3b3-c1f80ea82d1c%40orlitzky.com.
[sage-devel] "pulling" an older branch from the develop tree
I did not been pay close attention to the details of working with the develop tree and other repositories, and have a question: I would like to be able to clone an earlier sage release than what’s at the top of the tree. After poking the documentation, I think this would clone the previous release to the current (rc1) release. Is this correct? git clone git://github.com/sagemath/sage.git 9.0-rc0 Thanks! And apologies for lame questions… Justin -- Justin C. Walker Curmudgeon-at-large -- Network, n., Difference between work charged for and work done -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/116CF7BB-19DC-4CF8-8091-3B4D475A6483%40mac.com.
Re: [sage-devel] Buiding sage on a Raspberry Pi 4B
This pull request from last week on the pexpect repo has the news that Travis-CI added ARM64 support. - ARM64: Add ARM64 jobs in Travis-CI https://github.com/pexpect/pexpect/pull/612 See the recent Travis-CI blog posts about arm support (October 2019) and Power support (December 2019). - Multi-CPU architecture support for your builds https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support - Build your open source projects on IBM Power and IBM Z CPU architecture https://blog.travis-ci.com/2019-11-12-multi-cpu-architecture-ibm-power-ibm-z -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/f6f7c4fa-25bc-465d-9aff-9c73bb3916aa%40googlegroups.com.
Re: [sage-devel] Buiding sage on a Raspberry Pi 4B
Mon 2019-12-30 15:24:59 UTC, Dima Pasechnik a écrit : > > Hoi Jaap, > > it's interesting to dig more into these segfaults, they might be due > to Rasberry Pi CPU being ARM, > and we didn't test Sage on ARM for the last 4-5 years. > In fact our download site has an arm section: http://files.sagemath.org/linux/arm/index.html where the last binary offered is sage-6.9-armv7l-Linux-Ubuntu_12.10.tar.gz A little over a year ago, end of Nov 2018, one user built SageMath 8.4 on ARM and asked a question on Ask Sage about packaging it up. How to pack sage-8.4 armv7l built as compressed re-distributable binaries? https://ask.sagemath.org/question/44489 We could think about setting up ARM patchbots and an ARM buildbot. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/c26c1c20-61d8-42df-996a-fd8662880893%40googlegroups.com.
Re: [sage-devel] Buiding sage on a Raspberry Pi 4B
Hoi Jaap, it's interesting to dig more into these segfaults, they might be due to Rasberry Pi CPU being ARM, and we didn't test Sage on ARM for the last 4-5 years. Dima On Mon, Dec 30, 2019 at 11:17 PM Jaap Spies wrote: > > Why? Because it is possible. And the OS Raspbian is distributed with a > version of Mathematica 12.0 > > First attempt was building sage-8.9. Just did a 'make' after downloading. The > RPi 4 showed unstable. > The little computer stalled a few times. Power off and power on. After 12 > hours there was a running sage. > Building the docs failed consistently. I ran a few tests. > > Secondly I did a "MAKE='make -j4' make". After a few hick-ups I changed to > 'make -j3' and got sage running, but building the docs > failed on the same spot. > > Third was a try to build sage-9.0.beta9 with 'make -j3'. Again a few freezes, > but the building of the docs succeeded! > The same with sage-9.0.beta10. Testing with 'make ptestlong' lasted long. It > was good my RPi 4 had active cooling with temperatures > up to 75 degrees Celcius. There were 60 failures, some segmentation faults > some Time Outs. > Most of the errors were resolved by running a bash script to test files > individually. > > The building of sage-9.0.rc0 ended in problems with building scipy. My idea > of computers being deterministic is chocked. > I started with a clean source. And to my surprise only a few hick-ups and > after 'make ptestlong' 56 failed tests. > Most of them were resolved. See above. > > As we speak now sage-9.0.rc1 is doing a 'make ptestlong'. Probably will > finish in a few hours. > > My conclusion so far: Sage can be built on a Rarpberry Pi 4, but certainly > not unattended. > > Most remarkable: > Saved trace to /home/pi/.sage/crash_logs/crash_s8ljau3w.log > > Unhandled SIGSEGV: A segmentation fault occurred. > This probably occurred because a *compiled* module has a bug > in it and is not properly wrapped with sig_on(), sig_off(). > Python will now terminate. > > > ** > > sage -t --long --warn-long 248.7 > src/sage/rings/function_field/function_field.py # Timed out > sage -t --long --warn-long 248.7 > src/sage/schemes/elliptic_curves/ell_rational_field.py # Timed out > sage -t --long --warn-long 248.7 > src/sage/schemes/elliptic_curves/isogeny_class.py # Killed due to > segmentation fault > sage -t --long --warn-long 248.7 src/sage/modular/pollack_stevens/modsym.py > # Timed out > sage -t --long --warn-long 248.7 > src/sage/rings/function_field/function_field_valuation.py # Timed out > sage -t --long --warn-long 248.7 src/sage/rings/padics/padic_base_leaves.py > # Timed out > sage -t --long --warn-long 248.7 src/sage/combinat/tableau.py # Killed due > to segmentation fault > sage -t --long --warn-long 248.7 > src/sage/rings/valuation/augmented_valuation.py # Timed out > sage -t --long --warn-long 248.7 > src/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py # Timed > out > sage -t --long --warn-long 248.7 > src/sage/combinat/root_system/root_lattice_realization_algebras.py # Killed > due to segmentation fault > sage -t --long --warn-long 248.7 > src/sage/modular/modform_hecketriangle/readme.py # Killed due to > segmentation fault > sage -t --long --warn-long 248.7 src/sage/structure/coerce_dict.pyx # 1 > doctest failed > sage -t --long --warn-long 248.7 > src/sage/schemes/elliptic_curves/constructor.py # Timed out > sage -t --long --warn-long 248.7 > src/sage/combinat/crystals/kirillov_reshetikhin.py # Timed out > sage -t --long --warn-long 248.7 src/sage/combinat/shifted_primed_tableau.py > # Killed due to segmentation fault > sage -t --long --warn-long 248.7 src/sage/categories/finite_monoids.py # > Timed out > sage -t --long --warn-long 248.7 > src/sage/combinat/root_system/integrable_representations.py # Timed out > sage -t --long --warn-long 248.7 > src/sage/combinat/crystals/littelmann_path.py # Timed out > sage -t --long --warn-long 248.7 src/sage/rings/tests.py # Killed due to > segmentation fault > sage -t --long --warn-long 248.7 src/doc/ca/intro/index.rst # Timed out > sage -t --long --warn-long 248.7 src/sage/modular/abvar/homspace.py # Timed > out > sage -t --long --warn-long 248.7 src/sage/groups/libgap_morphism.py # Timed > out > sage -t --long --warn-long 248.7 > src/sage/rings/function_field/differential.py # Killed due to segmentation > fault > sage -t --long --warn-long 248.7 src/sage/combinat/posets/poset_examples.py > # Timed out > sage -t --long --warn-long 248.7 > src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py > # Timed out > sage -t --long --warn-long 248.7 > src/sage/algebras/lie_algebras/verma_module.py # Timed out > sage -t --long --warn-long 248.7 src/sage/rings/
[sage-devel] Buiding sage on a Raspberry Pi 4B
Why? Because it is possible. And the OS Raspbian is distributed with a version of Mathematica 12.0 First attempt was building sage-8.9. Just did a 'make' after downloading. The RPi 4 showed unstable. The little computer stalled a few times. Power off and power on. After 12 hours there was a running sage. Building the docs failed consistently. I ran a few tests. Secondly I did a "MAKE='make -j4' make". After a few hick-ups I changed to 'make -j3' and got sage running, but building the docs failed on the same spot. Third was a try to build sage-9.0.beta9 with 'make -j3'. Again a few freezes, but the building of the docs succeeded! The same with sage-9.0.beta10. Testing with 'make ptestlong' lasted long. It was good my RPi 4 had active cooling with temperatures up to 75 degrees Celcius. There were 60 failures, some segmentation faults some Time Outs. Most of the errors were resolved by running a bash script to test files individually. The building of sage-9.0.rc0 ended in problems with building scipy. My idea of computers being deterministic is chocked. I started with a clean source. And to my surprise only a few hick-ups and after 'make ptestlong' 56 failed tests. Most of them were resolved. See above. As we speak now sage-9.0.rc1 is doing a 'make ptestlong'. Probably will finish in a few hours. My conclusion so far: Sage can be built on a Rarpberry Pi 4, but certainly not unattended. Most remarkable: Saved trace to /home/pi/.sage/crash_logs/crash_s8ljau3w.log Unhandled SIGSEGV: A segmentation fault occurred. This probably occurred because a *compiled* module has a bug in it and is not properly wrapped with sig_on(), sig_off(). Python will now terminate. ** sage -t --long --warn-long 248.7 src/sage/rings/function_field/function_field.py # Timed out sage -t --long --warn-long 248.7 src/sage/schemes/elliptic_curves/ell_rational_field.py # Timed out sage -t --long --warn-long 248.7 src/sage/schemes/elliptic_curves/isogeny_class.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/modular/pollack_stevens/modsym.py # Timed out sage -t --long --warn-long 248.7 src/sage/rings/function_field/function_field_valuation.py # Timed out sage -t --long --warn-long 248.7 src/sage/rings/padics/padic_base_leaves.py # Timed out sage -t --long --warn-long 248.7 src/sage/combinat/tableau.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/rings/valuation/augmented_valuation.py # Timed out sage -t --long --warn-long 248.7 src/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py # Timed out sage -t --long --warn-long 248.7 src/sage/combinat/root_system/root_lattice_realization_algebras.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/modular/modform_hecketriangle/readme.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/structure/coerce_dict.pyx # 1 doctest failed sage -t --long --warn-long 248.7 src/sage/schemes/elliptic_curves/constructor.py # Timed out sage -t --long --warn-long 248.7 src/sage/combinat/crystals/kirillov_reshetikhin.py # Timed out sage -t --long --warn-long 248.7 src/sage/combinat/shifted_primed_tableau.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/categories/finite_monoids.py # Timed out sage -t --long --warn-long 248.7 src/sage/combinat/root_system/integrable_representations.py # Timed out sage -t --long --warn-long 248.7 src/sage/combinat/crystals/littelmann_path.py # Timed out sage -t --long --warn-long 248.7 src/sage/rings/tests.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/doc/ca/intro/index.rst # Timed out sage -t --long --warn-long 248.7 src/sage/modular/abvar/homspace.py # Timed out sage -t --long --warn-long 248.7 src/sage/groups/libgap_morphism.py # Timed out sage -t --long --warn-long 248.7 src/sage/rings/function_field/differential.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/combinat/posets/poset_examples.py # Timed out sage -t --long --warn-long 248.7 src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py # Timed out sage -t --long --warn-long 248.7 src/sage/algebras/lie_algebras/verma_module.py # Timed out sage -t --long --warn-long 248.7 src/sage/rings/padics/padic_valuation.py # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/rings/complex_number.pyx # Killed due to segmentation fault sage -t --long --warn-long 248.7 src/sage/geometry/fan.py # Timed out sage -t --long --warn-long 248.7 src/sage/rings/function_field/element.pyx # Timed out sage -t --long --warn-long 248.7 src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx # T
Re: [sage-devel] srange under python3
On Thu, Dec 26, 2019 at 1:10 PM chris wuthrich wrote: > > > I have a question about the future of srange under python 3, which changes > the behaviour of range. Probably this has been discussed before but I could > not find it. > > In 9.0.beta10 we have > > sage: range(1,3) > range(1, 3) > sage: srange(1,3) > [1, 2] > sage: sxrange(1,3) > > sage: [1..2] > [1, 2] > sage: type(range(1,3)), type(srange(1,3)), type(sxrange(1,3)), type([1..2]) > (, , , ) > > and no xrange anymore. > > Would it make sense to drop sxrange and make srange an iterator like range, > while keeping [a..b] as a list as suggested by its notation? I agree with this course of action. Perhaps it wouldn't be too late to do that for Sage 9.0? * Make srange an iterator class that works the same as Python 3's range (including support for len() and slicing) * Make sxrange a deprecated alias for srange * Keep [a..b] a list per its notation (i.e. nothing to do there) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34a4xN-xeu3yCkcoqU-xk7RyhJTcgg5KCno_X0B2kUnHcQ%40mail.gmail.com.
