Re: [sage-devel] Any interest in making building from source on Mac more robust?

Sorry it is "39571" everywhere in my instructions. -- 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

Re: [sage-devel] Any interest in making building from source on Mac more robust?

To be on the PR branch, execute git fetch upstream pull/35971/head:pr-35971 git checkout pr-35971 after you have already set the github repo sagemath/sage as "upstream" remote. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Any interest in making building from source on Mac more robust?

You are not on the branch of the PR: https://github.com/sagemath/sage/pull/39571 Are you? -- 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...@g

Re: [sage-devel] Re: Any interest in making building from source on Mac more robust?

Is your branch on the PR branch of https://github.com/sagemath/sage/pull/39571 ? It should be for the current release. I'll take the incremental testing approach. As a first set of questions: - On the Install from Source Code p

Re: [sage-devel] Re: Any interest in making building from source on Mac more robust?

https://github.com/sagemath/sage/pull/39571 is needed for successful build with the latest release. On Saturday, February 22, 2025 at 10:27:40 PM UTC+9 mwi...@gmail.com wrote: Thank you, Volker, for that proof of viability of building Sage on Apple silicon (an M2 Mini) and to Kwankyu on both a

[sage-devel] Re: Any interest in making building from source on Mac more robust?

Ah I forgot to mention: brew upgrade and source .homebrew-build-env before "make ..." -- 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...@go

[sage-devel] Re: Any interest in making building from source on Mac more robust?

But I still want to be able to do a clean build from source on current macOS versions. Are there developers in this community with similar interests? I would be interested in collaborating with you on making the build process on macOS more robust. My main machines are all macOS. I never thou

Re: [sage-devel] Re: A PR making changes to CI needs your attention

#39467 eliminates "minimal" CI testing: test building sage from source on platforms with minimal required system packages installed. See the relevant section on our installation guide: https://doc-release--sagemath.netlify.app/html/en/installation/source#software-prerequisites-and-recommended-p

[sage-devel] Re: A PR making changes to CI needs your attention

I object to the PR #39467, and prepared an alternative PR https://github.com/sagemath/sage/pull/39009 to restore the CI infrastructure to good shape. The PR #39009 is now ready for review. Please join in the discussion. -- You received this message because you are subscribed to the Google

[sage-devel] Re: Corrupted git submodule in sage repo

I remove the seemingly useless directory: subprojects/factory in the PR https://github.com/sagemath/sage/pull/39009 -- 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 t

[sage-devel] Re: Corrupted git submodule in sage repo

But there is nothing to commit! How can we fix the repo? By the way, what is this directory subprojects/factory for? Can we remove it? Removing the directory would fix the problem. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscr

[sage-devel] Re: Corrupted git submodule in sage repo

I could trace the problem to https://github.com/sagemath/sage/pull/37447 -- 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

[sage-devel] Corrupted git submodule in sage repo

Hi I noticed $ cd sage sage$ git submodule status fatal: no submodule mapping found in .gitmodules for path 'subprojects/factory' sage$ git status On branch develop Your branch is up to date with 'origin/develop'. nothing to commit, working tree clean I can fix the fatal error as follo

[sage-devel] A PR making changes to CI needs your attention

Please join in the discussion on https://github.com/sagemath/sage/pull/39467 -- 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.c

[sage-devel] A failure in FFLAS-FFPACK seemingly dependent on the system

If you experience the following failure (or not), please report Sage 10.5 with Python 3.10 on Ubuntu jammy to https://github.com/sagemath/sage/issues/39460 sage: N = matrix(Integers(7), 2, [1,2,3,4]) sage: N [1 2] [3 4] sage: N.rank() -

Re: [sage-devel] attempting to finish PR with flaky CI tests

On Tuesday, February 4, 2025 at 7:51:19 PM UTC+9 tobia...@gmx.de wrote: > I suggest to make the checks information only; the check report failed step, but the check itself passes always. I don't think this is a good idea. If some tests fail randomly, then that's an issue with the test and not

Re: [sage-devel] attempting to finish PR with flaky CI tests

The basic idea is not to fail a CI check if the PR branch is not the cause. Currently, (1) "Build & Test / test-long" sometimes fails. (2) It occurs frequently that one of "Build & Test using Conda(Meson) / Conda" checks fails. (1) is unfortunate, but this is our main engine checking the PR

Re: [sage-devel] attempting to finish PR with flaky CI tests

Do you also want to disable CI workflows that sometimes fail for intrinsic reasons? For example, the Build & Test workflow often fails to push the temporary Docker image that it builds (eg https://github.com/sagemath/sage/actions/runs/13036220999/job/36367766912). No. Just CI workflows that

Re: [sage-devel] Policy for closing abandoned PRs

On Saturday, January 25, 2025 at 5:35:47 AM UTC+9 Nils Bruin wrote: On Friday, 24 January 2025 at 11:28:42 UTC-8 axio...@yahoo.de wrote: To do this, it is very helpful that unfinished tickets are *not* closed, because this gives me the "interesting" tickets with a single click: I hide all the c

Re: [sage-devel] attempting to finish PR with flaky CI tests

On Friday, January 31, 2025 at 2:44:39 AM UTC+9 dim...@gmail.com wrote: You can just check whether CI failures are relevant to your branch, and if not, write so in comments. I think we should adopt a policy that promptly (no excuse) disable any CI check that fails due to reasons unrelated to

Re: [sage-devel] Policy for closing abandoned PRs

The reviewer may close unresponsive PRs with the label "r: invalid". By the way, "r" stands for resolution. Or we could make up a new label "r: unresponsive" (with one word). I propose to wait for 3 months before closing. That policy should apply for strictly unresponsive (with no apparent r

[sage-devel] Re: Proposal to allow downloads during build of optional packages

To be clear, note that we have two types of packages: standard and optional. Standard packages are by definition those packages installed by default. See https://doc-release--sagemath.netlify.app/html/en/developer/packaging#package-types The proposal is about allowing internet connection for o

[sage-devel] Re: binder and optional packages

On Wednesday, December 18, 2024 at 5:08:57 PM UTC+9 enriqu...@gmail.com wrote: I would like to know how to change Dockerfile in sage-binder-env to use optional packages. The sage-binder-env on the master and dev branches uses a docker image that contains a light-weight sage that has no capab

[sage-devel] Re: Time to show off your contributions in Sage 10.5 Release Tour

On Friday, December 13, 2024 at 6:54:51 PM UTC+9 Eric Gourgoulhon wrote: It seems that there is no longer any link towards the Release Tour from the front page https://www.sagemath.org/ Is this intended? I don't know what happened to what link. Kwankyu -- You received this message because yo

[sage-devel] Re: Time to show off your contributions in Sage 10.5 Release Tour

A style guide: - Be explicit and brief about the changes (of your contribution). - Keep links to PRs out of the sentences. Group them at the end of the paragraph. for easy reading of the release tour. -- You received this message because you are subscribed to the Google Groups "sage

[sage-devel] Re: Wanted: An updated Sage contributors world map

On Wednesday, November 13, 2024 at 4:39:43 AM UTC+9 sohamr...@gmail.com wrote: We can write a script using the GitHub API to automate changelog creation in the same format as the ones at https://www.sagemath.org/changelogs . The idea is to first retrieve the IDs of all merged PRs from GitHub

[sage-devel] Re: Curve() accepts incorrect arguments

Curve code does not check the dimension of the input ideal, as it is an expensive computation in general. But in this case, it was actually fixed recently (in Sage 10.5.rc0): sage: C=Curve(J);C ... ValueError: defining equations (=[x*y*z - t^2, x + 2*y + 3*z - t - 1]) define a scheme of dime

[sage-devel] Re: Curve() accepts incorrect arguments

sage: Ideal(J).dimension() 2 Curve code does not check the dimension of the input ideal, as it is an expensive computation in general. I think this should be documented in the docstring, though in general, it is user's responsibility to pass appropriate input. -- You received this message

[sage-devel] Time to show off your contributions in Sage 10.5 Release Tour

As usual, the webpage is at https://github.com/sagemath/sage/wiki/Sage-10.5-Release-Tour -- 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...@go

Re: [sage-devel] Defining MAKE='make -j4' is recommended?

On Wednesday, November 13, 2024 at 11:06:46 PM UTC+9 Michael Orlitzky wrote: On 2024-11-13 01:12:25, Kwankyu Lee wrote: > Hi, > > According to our installation guide: > > *One useful setting for this variable when building Sage is MAKE='make > -jNUM' to tell

[sage-devel] Defining MAKE='make -j4' is recommended?

Hi, According to our installation guide: *One useful setting for this variable when building Sage is MAKE='make -jNUM' to tell the make program to run NUM jobs in parallel when building. Note that some Sage packages may not support this variable.* and our main build scripts are sprinkled with

[sage-devel] Include TESTS in doc previews for PRs

Hi, The PR https://github.com/sagemath/sage/pull/38449 needs review. EXAMPLES are for users and TESTS are for developers. Hence it is natural to show rendered TESTS in doc previews for developers. Thank you for attention. Kwankyu -- You received this message because you are subscribed to th

[sage-devel] Re: strange part of the doc

The directory is anyway redundant. The PR https://github.com/sagemath/sage/pull/38895 is for removing it after doc build. -- 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 e

[sage-devel] Re: strange part of the doc

This was an attempt to change the mechanism https://github.com/sagemath/documentation/pull/27 It was merged, but the mechanism seems to be still there... I gave up. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group a

[sage-devel] Re: strange part of the doc

On Thursday, October 31, 2024 at 9:02:33 PM UTC+9 axio...@yahoo.de wrote: That would be good. If you navigate to https://doc.sagemath.org/ this is one of the first thing you would see. Compare with https://doc-release--sagemath.netlify.app/ doc.sagemath.org has a different mechanism genera

[sage-devel] Re: strange part of the doc

They are artifacts generated for the page https://doc.sagemath.org/html/en/tutorial/latex.html Perhaps they may be deleted after the doc is built... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivin

[sage-devel] Removal notice of a Sage installation mode

Hi, The installation mode "Using conda to provide system packages for the Sage distribution": https://doc-release--sagemath.netlify.app/html/en/installation/conda#using-conda-to-provide-system-packages-for-the-sage-distribution will be removed by the pr #38728. -- You received this message

[sage-devel] Re: Removal notice of a Sage installation mode

The pr is at https://github.com/sagemath/sage/pull/38728 -- 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 disc

Re: [sage-devel] A new logo?

This seems to contain a definitive answer to the question about the meaning of the logo: https://ask.sagemath.org/question/7667/geometric-name-of-sage-logo-existence-of-dual/ -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from th

Re: [sage-devel] A new logo?

On Monday, October 21, 2024 at 8:42:44 PM UTC+9 kcrisman wrote: On Monday, October 21, 2024 at 12:08:55 AM UTC-4 Kwankyu Lee wrote: On Monday, October 21, 2024 at 8:47:02 AM UTC+9 Michael Orlitzky wrote: * The icosahedron strikes me as an instance of "hey give me the name of a cool

Re: [sage-devel] A new logo?

On Monday, October 21, 2024 at 3:12:50 PM UTC+9 seb@gmail.com wrote: > *I designed the suggested logo to reflect the identity.* My interpretation of the existing logo is a visualization of the Euler characteristic formula (pointing out edges and vertices). So it is a non-planar graph. I

[sage-devel] Re: Using Sage on Windows

On Monday, October 21, 2024 at 3:23:16 PM UTC+9 seb@gmail.com wrote: > *The third version is ready:* I tested it on Saturday, but with the same result as before. Right. I missed your point. The installer's check for WSL installation was deficient. Now I made an improvement. Let me know how

Re: [sage-devel] A new logo?

On Monday, October 21, 2024 at 8:47:02 AM UTC+9 Michael Orlitzky wrote: * The icosahedron strikes me as an instance of "hey give me the name of a cool math shape" that has nothing to do with sage itself The icosahedron in the current logo looks broken to me. I wonder what was the intention.

Re: [sage-devel] A new logo?

On Monday, October 21, 2024 at 5:28:08 AM UTC+9 seb@gmail.com wrote: In addition I think there should be more reasons for changing the logo than just: "*I don't like it anymore!*". At least I didn't like the sci-fi font from 2009 :-) https://groups.google.com/g/sage-devel/c/yfv23vSAj8E/m

[sage-devel] Re: A new logo?

On Monday, October 21, 2024 at 2:04:29 AM UTC+9 marc@gmail.com wrote: I think that is an interesting start. However, I think it would be a good idea (and also very helpful to me) for you to read this: https://developer.apple.com/design/human-interface-guidelines/app-icons Thanks. That is

[sage-devel] Re: A new logo?

The background is actually transparent. -- 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 we

[sage-devel] A new logo?

Hi As some of you who tried https://github.com/sagemath/sage-binder-env/releases/tag/v10.4 may have noticed, I did a bit creative work on icons. Thus I came up with an idea of a new logo for Sage. Check out the attached png file. Personally I dislike the current Sage logo, both the icon and

[sage-devel] Re: Using Sage on Windows

The third version is ready: https://github.com/sagemath/sage-binder-env/releases/tag/v10.4 -- 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...@

[sage-devel] Re: Using Sage on Windows

On Saturday, October 19, 2024 at 6:03:05 AM UTC+9 seb@gmail.com wrote: Have you looked for overlap with Julian's work? No. I had no time :-) My installer installs a minimized Sage (no build facility, no optional package, no local docs), basically the same sage that you get from the sage-bi

[sage-devel] Re: Using Sage on Windows

On Friday, October 18, 2024 at 4:45:39 PM UTC+9 seb@gmail.com wrote: > *I auto-created a powershell script to make this even easier ...* Interesting! How did you auto-create that? With a translation tool? Just by github action :-) > *Needs test.* I tried it in a Hyper-V guest running a

[sage-devel] Re: Using Sage on Windows

On Thursday, October 17, 2024 at 3:00:18 PM UTC+9 Kwankyu Lee wrote The wsl image tar file is of size about 6GB. It would be nice if we have a public file server to accommodate the tar file. The gzipped file is just 1.8GB. I may use release assets for some time. -- You received this

[sage-devel] Re: Using Sage on Windows

Another alternative would be to import the docker image as a WSL distribution. From a user perspective, this would be simply setting up WSL, downloading the docker image as a tar file and then run wsl --import SageMath . The tar file could be automatically generated from the docker image upon

[sage-devel] Re: Error during the complitation (make) on WSL

Hi, Here is a simplified guide: https://github.com/sagemath/sage/pull/38659 Not sure if this would be helpful to your case. Any comments are welcome. Please start with https://doc-pr-38659--sagemath.netlify.app/html/en/installation/troubles -- You received this message because you are subsc

[sage-devel] Re: Proposal: ci codecov/patch reports but not fail

(3) We keep our current practice (add doctests for major functionality, and later doctests are added for broken cases). We change codecov/path to report but not fail. (3) is implemented in the PR https://github.com/sagemath/sage/pull/38812. -- You received this message because you are sub

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Monday, October 7, 2024 at 6:38:34 PM UTC+9 oscar.j@gmail.com wrote: ... There would also be a strong incentive to try to carve out a meaningful subset of Sage for end-users that was more portable ... "portable" sounds a good adjective to characterize distribution packages. Another may

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Monday, October 7, 2024 at 12:24:04 AM UTC+9 marc@gmail.com wrote: I would say that the motivation is to make it possible for a developer to include a self-contained portion of sage in a separate project without having to make that project as large as a full Sage distribution. OK. That

[sage-devel] Re: Proposal: ci codecov/patch reports but not fail

There are ways to "bloat" the set of doctests with minimal impact. For example, we could create a file "TESTS.py" (for example) in a Sage module, consisting only of doctests. It would not be included in the reference manual, not visible when someone does "X.my_favorite_method?" or "X.my_favor

[sage-devel] Re: Proposal: ci codecov/patch reports but not fail

But I don't know how big a problem the codecov issue is ... We want to regard the check failure as there is a problem with the PR that the author should resolve. Currently the codecov failure triggers the check failure, but no reviewer and no author regard the codecov failure as a pro

[sage-devel] Re: Proposal: ci codecov/patch reports but not fail

No comment will be construed as no objection. -- 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 t

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

We are observing disadvantage of a long thread. At some point, other participants forget the context in which a participant write a comment. Dima and I were talking about a fictional sagemath-number-theory distribution package. I imagined a user/developer who installed sagemath-number-theory, a

[sage-devel] Re: ERROR [transfer|run:135]: [Errno 404] Not Found when downloading cython-3.0.11.tar.gz

I think I experienced the same phenomenon (getting stuck) once before. Later it disappeared perhaps after "make distclean" or something. I don't know why. You may try again after removing all files in /home/slabbe/GitBox/sage/upstream/ -- You received this message because you are subscribed

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

It seems to me that one of the main innovations of sage (among other CAS) was to make writing doctests really easy *and* keep them together with the code *and* make testing them *while developing* very straightforward. True! The final of these three points would be broken *by encouraging d

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

I can imagine this: sagemath-number-theory won't have the coding theory portion of the sage library. Hence developers for sagemath-number-theory could test their favorite distribution package quicker. -- You received this message because you are subscribed to the Google Groups "sage-devel" gr

[sage-devel] Proposal: ci codecov/patch reports but not fail

Hi, Currently ci is in good shape except codecov/patch. codecov/patch works well: it reports the coverage change, and fails for a PR that does not test every code path. However, it is a problem that codecov/patch failure make the whole check for the PR fail. *It is not our coding standard tha

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

In my mind it could make sense for there to be a sagemath-minimal package which from a user perspective represents a "minimal installation of Sage" in comparison to say a package called sagemath-full. sagemath-standard is your sagemath-full. I think distribution packages in the current des

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

There are two factors that forms a distribution package: (a) mathematical contents of the code and (b) dependencies (external software packages) that supports the code. Some distribution packages are named after mathematical contents and others are named after the main dependency. Distribution

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Sunday, September 29, 2024 at 5:31:15 PM UTC+9 axio...@yahoo.de wrote: Please don't fragment this discussion. It seems productive to me currently. According to the recent survey, visitors to sage-devel seem to get tired of lengthy technical discussions with only a few people involved. This

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

I welcome this discussion on the design of modularized distribution packages. Perhaps Matthias has his design fixed in his plan. But I believe the modularization project would succeed only when many sage developers understand and accept the design. Hence it is crucial that we have open discus

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Saturday, September 28, 2024 at 3:52:51 PM UTC+9 axio...@yahoo.de wrote: However, this PR introduces a new kind of file, `all__sagemath_categories.py`, into (almost?) *every* subdirectory of src. Thus, it seems to me that this affects almost all developers - after all these files have to b

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

Everyone here, According to the recent survey, people complain lengthy technical discussions happening in sage-devel, that many of them find irrelevant to their interests. If a thread in sage-devel involves a technical discussion, how about opening a new Discussion in https://github.com/sagem

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

On Saturday, September 28, 2024 at 6:25:07 AM UTC+9 axio...@yahoo.de wrote: ... All of these are then imported by src/sage/all__sagemath_categories.py I don't think that I understand the purpose of sagemath_categories. Do you know the purpose of files like `all__xxx`? The purpose of these file

Re: [sage-devel] trouble installing sage

On Friday, September 27, 2024 at 9:05:49 AM UTC+9 anne1.s...@gmail.com wrote: A miracle!!! Sage has installed on MacOS 15.0. I uninstalled homebrew from /usr/local. Congratulations! So it was just another instance of homebrew in /usr/local/ that caused all troubles. I will appreciate if y

Re: [sage-devel] trouble installing sage

This ld: warning: ignoring file '/usr/local/Cellar/openblas/0.3.28/lib/libopenblasp-r0.3.28.dylib': found architecture 'x86_64', required architecture 'arm64' is significant. Your hombrew openblas is not compiled for arm64. This is strange. Try file /usr/local/Cellar/openblas/0.3.28/lib/libo

Re: [sage-devel] trouble installing sage

On Thursday, September 26, 2024 at 8:49:24 AM UTC+9 anne1.s...@gmail.com wrote: Hi Dima, Yes, I have openblas installed via brew and just reinstalled it again and get the same error message. If you get the same error message, then it means that Sage is not using hombrew openblas. What does "

Re: [sage-devel] trouble installing sage

The error message in your log [spkg-install] building 'kiwisolver._cext' extension [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310 [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py/src [spk

Re: [sage-devel] trouble installing sage

The error message in your log [spkg-install] building 'kiwisolver._cext' extension [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310 [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py/src [

Re: [sage-devel] trouble installing sage

In the lines of your log [spkg-install] building 'kiwisolver._cext' extension [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310 [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py/src [spkg-ins

Re: [sage-devel] trouble installing sage

In the lines of your log ... [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310 [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py [spkg-install] creating build/temp.macosx-10.15-x86_64-cpython-310/py/src [spkg-install] *gcc -Wno-unused-result -Wsign-compare -W

Re: [sage-devel] trouble installing sage

I would also try sudo xcode-select --reset -- 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

Re: [sage-devel] trouble installing sage

On Wednesday, September 25, 2024 at 1:16:41 PM UTC+9 Kwankyu Lee wrote: According to your kiwisolver-1.4.5 log, [spkg-install] py/src/constraint.cpp:8:10: fatal error: 'algorithm' file not found [spkg-install] 8 | #include [spkg-install] | ^~~ [spkg-install] 1 error genera

Re: [sage-devel] trouble installing sage

According to your kiwisolver-1.4.5 log, [spkg-install] py/src/constraint.cpp:8:10: fatal error: 'algorithm' file not found [spkg-install] 8 | #include [spkg-install] | ^~~ [spkg-install] 1 error generated. [spkg-install] error: command '/usr/bin/gcc' failed with exit code 1 your gcc

Re: [sage-devel] trouble installing sage

I get $ gcc --version Apple clang version 14.0.0 (clang-1400.0.29.202) Target: x86_64-apple-darwin21.6.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin What do you get? -- You received this message because you are subscribed to the Google Groups "sage-devel" grou

Re: [sage-devel] trouble installing sage

Is Xcode command line tools up to date? If not, do xcode-select --install -- 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.

Re: [sage-devel] trouble installing sage

Though Sage officially supports python 3.9 to python 3.12, in my experience, python 3.9 is "too old" and python 3.12 is somewhat "too new", in the sense that packages on which sage depends on may not work well with them. So I suggest to try ./configure --with-python=PYTHON3 where PYTHON3 is t

Re: [sage-devel] trouble installing sage

Uploading the logs of the failed packages /Applications/sage/logs/pkgs/ipykernel-6.27.1.log /Applications/sage/logs/pkgs/scipy-1.12.0.log would help. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receivi

[sage-devel] Re: Error Building from Source

Hi, It is unusual to pick "/home/username/.sage/sage" as the sage root directory. We recommend "/home/username/sage/sage". Kwankyu -- 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,

Re: [sage-devel] trouble installing sage

Hi Anne, The PR https://github.com/sagemath/sage/pull/38659 aims to simplify the installation instructions in README. As you seem to have a new macOS, would you try the guide in the new README on your platform? I have no idea about the cause of your troubles though. Kwankyu -- You received

Re: [sage-devel] Results of the Survey: Governance and Community building

Many complain that installing Sage is too difficult. I believe that that is also partially due to our complicated installation guide, which is painful to follow. PR https://github.com/sagemath/sage/pull/38659 aims to reduce the pain. -- You received this message because you are subscribed to

[sage-devel] Re: coverage CI is broken

PR https://github.com/sagemath/sage/pull/38687 needs review. -- 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 thi

[sage-devel] Re: Policy discussion about blocking others on Github

Thank John for the response. I have other questions in https://groups.google.com/g/sage-devel/c/cLnRyofH0lw/m/S__tbpV1AgAJ. They are about the period during which the blocking is effective. As the proposed policy from CoCC is about the resolution of the blocking, I think the policy should be s

[sage-devel] Re: Policy discussion about blocking others on Github

All mentions of "SageMath" seem redundant and may be removed from the paragraph. ... If the blocked person does not cooperate, the committee may sanction them. "them" -> "him or her". What is the possible sanction? I think the content of the sanction should be explicit and actionable as t

[sage-devel] Re: Policy discussion about blocking others on Github

A practical issue related with this discussion is as follows. If a member B is blocked by another member A, and there is a PR created by A. Then does B still (1) have the full rights to participate in the review process for the PR? Or (2) B's rights are suspended for the PR? If (1), we should p

[sage-devel] Re: Package upgrade PRs waiting for review

On Friday, September 6, 2024 at 3:00:47 PM UTC+9 tobia...@gmx.de wrote: The cython constraint in scipy is for build-time. Sagelib only cares about the fact that scipy is installed in the same venv, not how you install or build it. In fact, pip uses build isolation by default, or you may install

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

>Now back in sage, sage chose to be compatible with python's behavior in >x^(1/3) for whatever x that represents a number in the complex field, say x >= -1, RR(-1), CC(-1), QQbar(-1). For x = ZZ(-1), QQ(-1), they chose to >return symbolic expression (-1)^(1/3), which again converted to the sa

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

ZZ and QQ live in their own worlds (sigh). sage: ZZ(8)^(1/3) 2 sage: ZZ(-8)^(1/3) 2*(-1)^(1/3) sage: ZZ(1)^(1/3) 1 sage: ZZ(-1)^(1/3) (-1)^(1/3) sage: QQ(8)^(1/3) 2 sage: QQ(-8)^(1/3) 2*(-1)^(1/3) sage: QQ(1)^(1/3) 1 sage: QQ(-1)^(1/3) (-1)^(1/3) >>> RR(ZZ(-8)^(1/3)) ... TypeError: unable to

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

On Wednesday, September 4, 2024 at 1:41:30 PM UTC+9 Nils Bruin wrote: ... it may well depend on whether you're more algebraically or analytically oriented. Yes. That may be a way to reconcile the conflicting views. We may explicitly introduce technical distinction of "analytical fields" and "

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

On Wednesday, September 4, 2024 at 1:41:30 PM UTC+9 Nils Bruin wrote: .. Indeed, Magma's algebraic closure of QQ does not use an embedding into CC but instead tracks conjugate labels using a large finite field. You mean a large number field? >From QQbar doc: As with many other implementati

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

On Wednesday, September 4, 2024 at 12:22:33 PM UTC+9 Nils Bruin wrote: On Tuesday 3 September 2024 at 19:44:43 UTC-7 Kwankyu Lee wrote: I think that only valid argument for AA(-1)^(1/3) = -1 is that it is the status quo. It is just human that likes what she/he used to. Removing inconsistency

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

On Wednesday, September 4, 2024 at 3:05:19 AM UTC+9 dim...@gmail.com wrote: On Tue, Sep 3, 2024 at 5:08 PM Kwankyu Lee wrote: > > > That in Python one has non-real value for (-1)**(1/3) is > two things: 1/3 is actually a float, and absence of typing. > These are a

Re: [sage-devel] Re: QQbar(-1)^(1/3) != AA(-1)^(1/3)

That in Python one has non-real value for (-1)**(1/3) is two things: 1/3 is actually a float, and absence of typing. These are artifacts of the programming language, and make little sense mathematically. Do you mean that the value of (-1)**(1/3) is arbitrarily chosen, regardless of the mat

  1   2   3   4   5   6   7   8   9   10   >