[sage-devel] Re: command not found errors from configure

Oh. And I think the default value should probably be set with: PYTHON_FOR_VENV=/usr/bin/false - Marc On Saturday, May 4, 2024 at 5:54:55 PM UTC-5 Marc Culler wrote: > It is disturbing when one sees "command not found" errors in a configure > script. That is what happens

[sage-devel] command not found errors from configure

It is disturbing when one sees "command not found" errors in a configure script. That is what happens with 10.4.beta5. After tracing it down I found that they are coming from lines like: *if "${PYTHON_FOR_VENV}" -c "import sys; sys.exit(sys.version_info.minor < 11)"* *then :* The

[sage-devel] testing optional packages

I don't know what the expectations are for testing optional packages, but in 10.4.beta4 when I run: ./sage -t venv/lib/python3.11/site-packages/symengine I get the exception: NameError: name 'test_sage_conversions' is not defined - Marc -- You received this message because you are

Re: [sage-devel] Re: help menu in jupyter notebook

Yes, I was only talking about really just running Sage locally. - Marc. On Friday, April 26, 2024 at 7:54:38 PM UTC-5 Nils Bruin wrote: > On Friday 26 April 2024 at 15:44:22 UTC-7 marc@gmail.com wrote: > > I don't see what difference the choice of port makes to a user. It is not >

Re: [sage-devel] Re: help menu in jupyter notebook

The jupyter server operates on the loopback interface which has IP address 127.0.0.1 and IP name localhost. The cocoserver uses that same interface. Jupyter tries to get port and if that is busy it hunts for a nearby port that is not in use. The cocoserver uses an arbitrary

Re: [sage-devel] Re: help menu in jupyter notebook

Yes, I meant MB. Thanks. There are other issues with viewing local documentation files in a browser. On Ubuntu, Chrome and Firefox are packaged as snaps. A snap is not allowed to read a file:// url which is not in the user's home directory. As long as sage is installed in the user's home

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

riable is not used in those cases, but I don't know why not. - Marc On Thursday, April 25, 2024 at 11:30:52 PM UTC-5 Marc Culler wrote: > This looks pretty complicated. > > I used XCode 15.0.1 to build the macOS SageMath-10-3 app for Arm and XCode > 13.4 for Intel. I got "duplicate

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Fri, Apr 26, 2024 at 8:02 AM Dima Pasechnik wrote: > On Thu, Apr 25, 2024 at 4:36 PM wrote: > > you might also like to know that in 2000 I asked whether we can have > libgap :P > > https://www.gap-system.org/ForumArchive/Pasechni.1/Dmitrii.1/using_GA.1/1.html > It > Thank you! It is a

[sage-devel] Re: help menu in jupyter notebook

Another drawback of linking to online documentation is that the online documentation is always for the current release version of Sage, not the Sage that the user happens to be running,. I have a suggestion to improve the situation, which is to do what the Sage_macOS app does. The app

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

of >>>> C >>>> code. >>>> >>>> The calls to xcode-select were added in PR#36599 >>>> <https://github.com/sagemath/sage/pull/36599> in order to force XCode >>>> to use Apple's ld-classic linker instead of ld when their new

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

he dialog. The error message appears in >>>>> the terminal when running sage in a command line, which is annoying >>>>> and/or >>>>> alarming to someone with no plans to do anything involving compilation of >>>>> C >>>>> code. &

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

nstead of ld when their new version of ld >> was totally broken. This is done by adding -ld_classic to LDFLAGS. >> >> *Note to people who worked on PR #36599* (@jhpalmieri and @mkoeppe): I >> think Apple's new linker is working now, so it is probably no longer >> necess

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

April 25, 2024 at 9:17:35 AM UTC-5 Marc Culler wrote: > Another amusing quote, this time from the sbrk man page on macOS: > > > The brk and sbrk functions are historical curiosities left over from > > earlier days before the advent of virtual memory management. > >

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

stems). - Marc On Thursday, April 25, 2024 at 9:03:30 AM UTC-5 Marc Culler wrote: > On Thursday, April 25, 2024 at 8:28:48 AM UTC-5 Dima Pasechnik wrote: > > Essential components of sagelib such as GAP, Singular, don't run on > native Windows > > > I was amused to find the following

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Thursday, April 25, 2024 at 8:28:48 AM UTC-5 Dima Pasechnik wrote: Essential components of sagelib such as GAP, Singular, don't run on native Windows I was amused to find the following statement on the GAP forum from 2005: >

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Thu, Apr 25, 2024 at 8:28 AM Dima Pasechnik wrote: > On Thu, Apr 25, 2024 at 1:28 PM Nathan Dunfield > wrote: > > > > On Wednesday, April 24, 2024 at 10:14:09 PM UTC-5 Matthias Koeppe wrote: > > > > Yes, native Windows would clearly be a very important target. > > > > > > As a data point,

[sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

DFLAGS. *Note to people who worked on PR #36599* (@jhpalmieri and @mkoeppe): I think Apple's new linker is working now, so it is probably no longer necessary and not a good idea to force use of ld_classic. - Marc On Tuesday, April 23, 2024 at 10:45:54 PM UTC-5 Marc Culler wrote: That was it!

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Wed, Apr 24, 2024 at 2:26 PM Oscar Benjamin wrote: > Presumably though a hypothetical person who wants CyPari2 but not all of > Sage can already just use CyPari so that person is already well served. > That hypothetical person could also use CyPari2 if they didn't care about memory leaks and

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

:27, Marc Culler wrote: > > > > The projects that will really benefit from modularization will be those > that provide their own limited mathematical context. Developers of such > projects will be able to choose which parts of Sage are relevant to their > specific context.

Re: [sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

On Wednesday, April 24, 2024 at 8:05:15 AM UTC-5 Dima Pasechnik wrote: running Cython in sage prompt or in Sage Jupyter notebook has nothing to do with -i option. I realize that. But it looked to me like those variables are being set in the sage-env script *primarily* to support sage -i.

Re: [sage-devel] Question: why does /usr/bin/gcc get called during Sage startup?

On Tuesday, April 23, 2024 at 11:17:49 PM UTC-5 Marc Culler wrote: I wonder if the Sage community would be willing to reconsider the idea of having one entry point for every function provided by SageMath, I won't speak for the community, but I reconsidered this and I decided that it would

Re: [sage-devel] Question: why does /usr/bin/gcc get called during Sage startup?

On Tuesday, April 23, 2024 at 8:58:58 PM UTC-5 Dima Pasechnik wrot It's not quite correct to say that a C, or other, compiler is not required to run Sage. Sage allows you to define, build, load, and run Cython extensions without leaving Sage, thus, it needs to call a compiler after

[sage-devel] Re: Question: why does /usr/bin/gcc get called during Sage startup?

m/sagemath/sage/commit/69213d74ead4e93687cf61f214b0d96dd3f9885a > > Maybe you can workaround this by setting AS=as and LD=ld in > sage-env-config. > > HTH, > Gonzalo > > > On Tuesday, April 23, 2024 at 3:48:18 PM UTC-3 Marc Culler wrote: > >> I discovered, b

[sage-devel] Question: why does /usr/bin/gcc get called during Sage startup?

I discovered, by installing the Sage_macOS app on a pristine macOS system, that somehow, somewhere, in Sage's startup sequence there is a call to gcc. This is true whether Sage is being started from a command line or a notebook. On such a macOS system /usr/bin/gcc exists, but calling it

[sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Tuesday, April 23, 2024 at 4:07:37 AM UTC-5 Tobias wrote: In reply to the comment ( https://github.com/sagemath/sage/pull/36676#issuecomment-2067371677) once the modularization is in place, it will impose wide-ranging constraints on what functions from other modules you are able to use.

Re: [sage-devel] Re: Urgent and important: Please vote on disputed PR #36964 (next step of the modularization project)

On Sunday, April 21, 2024 at 9:42:24 AM UTC-5 Nathan Dunfield wrote: For the statements in this thread, I don't see any contradictions about the definition of the "normal Python way of doing things". My understanding of that term is to post *self-contained* binary wheels to PyPI for all

Re: [sage-devel] Re: VOTE: Revert merged PR with unreviewed dependencies

On Thursday, April 18, 2024 at 12:47:36 PM UTC-5 David Roe wrote: On Thu, Apr 18, 2024 at 1:43 PM Matthias Koeppe wrote: I will first note that the title of this post is misleading. Everything that was merged has been reviewed -- as noted, many months ago. I agree that everything was

[sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

+1 on making python_build a standard package. - Marc On Tuesday, April 9, 2024 at 10:44:36 PM UTC-5 Matthias Koeppe wrote: > We added python_build as an optional "pip" package (see > https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types > for > the

Re: [sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

On Monday, April 15, 2024 at 7:03:27 AM UTC-5 Michael Orlitzky wrote: The solution for users is pretty simple. You should be able to install a sage that works and will remain working with one command using homebrew, conda, guix, etc. The reason you can't is ... I would just mention that macOS

Re: [sage-devel] Mysterious .sage behavior

> I must say I don't know what kind of problems these versioned names are > meant to solve. > > > > >On 31 March 2024 15:23:24 CEST, Marc Culler <https://groups.google.com/>> wrote : > > >if [ -z "$IPYTHONDIR" ]; then > > # We hardcode a ve

[sage-devel] Mysterious .sage behavior

This is a follow-up to a user's query in a Sage_macOS issue. The current sage-env script contains the excerpt below. It seems pretty confusing that Sage would create a directory named .sage/ipython-5.0.0 when Sage is shipping IPython 8.18.1. What would be wrong with calling the directory

Re: [sage-devel] Re: xz/liblzma has been compromised

n general, just ssh on certain linux distros. I would NOT suggest that "for your security" Sage should stop supporting linux. - Marc On Saturday, March 30, 2024 at 9:08:45 AM UTC-5 Marc Culler wrote: > > Potentially, any tarfile we host may contain an exploit. > > Po

Re: [sage-devel] Re: xz/liblzma has been compromised

> Potentially, any tarfile we host may contain an exploit. Potentially, any file may contain an exploit. This hack specifically targeted ssh. When used by ssh to verify keys, the hacked liblzma would validate certain invalid keys, allowing a "back door" for a particular bad actor to login to

[sage-devel] Downloads

In case anyone is interested ... The SageMath 10.3 app for macOS has been downloaded 684 times since it was released on Sunday. The SageMath 10.2 app was downloaded 8685 times since its release about 4 months ago. For both versions, Arm downloads outnumber Intel by about 2 to 1. Source:

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

is writing? Is there a reason why he is writing a kernel when one already exists? Obviously I have no idea what I am talking about and am publicly revealing my ignorance. - Marc On Friday, March 22, 2024 at 12:29:56 PM UTC-5 Marc Culler wrote: > I wasn't advocating anything l

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

I wasn't advocating anything like that. Certainly I don't think that pari-jupyter should be "killed". I am assuming that pari-jupyter is or will be a package that can be installed with pip. And I am also assuming that it has no direct interaction with Sage. Are those assumptions wrong? If

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

If one has Sage installed with the pari-jupyter package installed in Sage and one wants to run pari-jupyter, what does one do? Is it equivalent to just installing pari-jupyter with pip and starting it up in the normal way? Does pari-jupyter use any components of Sage? If the answers are

[sage-devel] Re: Vote: changes to Sage's Code of Conduct

+1 On Thursday, March 21, 2024 at 11:51:40 AM UTC-5 John H Palmieri wrote: > Dear Sage community, > > As announced at > https://groups.google.com/g/sage-devel/c/Xf6dbPLmKPY/m/p88auKlBAwAJ, I > propose some changes to the Code of Conduct. Those changes have been > discussed and modified based

[sage-devel] Re: Jupyter Lab Sage menu

It would also be a good idea to open the javascript console and see if there are errors being reported around the time when the menu disappears. - Marc On Wednesday, March 6, 2024 at 8:20:00 PM UTC-6 Marc Culler wrote: > Viviane, > > If you do a shift-reload (or whatever makes you

[sage-devel] Re: Jupyter Lab Sage menu

Viviane, If you do a shift-reload (or whatever makes your browser clear its cache) does that make the menu come back? - Marc On Wednesday, March 6, 2024 at 8:11:45 AM UTC-6 Viviane Pons wrote: > Dear all, > > I am working on a conda distribution of sage with jupyter lab. My conda >

Re: [sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

I see. Thanks. - Marc On Wed, Feb 28, 2024 at 6:49 PM Kwankyu Lee wrote: > > > On Thursday, February 29, 2024 at 8:35:24 AM UTC+9 Marc Culler wrote: > > I have a proposal: It should be forbidden to call for a vote on a proposal > before there has been a discu

[sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

I have a proposal: It should be forbidden to call for a vote on a proposal before there has been a discussion. Without a chair, it would be impossible for this group to follow Robert's Rules of Order, even approximately. But the basic process should still be the same. The rules are designed

[sage-devel] Re: Question about the sage venv.

On Thursday, December 7, 2023 at 5:04:25 PM UTC-6 Matthias Koeppe wrote: Sure, but that would preclude using the same SAGE_LOCAL for an installation with venv over a system python and an installation of SPKG python. I don't understand. The bash script sage/venv/bin/sage calls

[sage-devel] Re: Question about the sage venv.

On Thursday, December 7, 2023 at 2:31:24 PM UTC-6 Matthias Koeppe wrote: > The venv would always contain a pyvenv.cfg file. Could you explain why this matters for what you have in mind? It is not essential. It is just cleaner and more uniform. I think it is misleading to have something

[sage-devel] Re: Question about the sage venv.

e exceptions because they already set the rpaths, to a subdirectory of the python package named .dylibs. - Marc On Thursday, December 7, 2023 at 12:17:00 PM UTC-6 Matthias Koeppe wrote: > On Thursday, December 7, 2023 at 10:04:14 AM UTC-8 Marc Culler wrote: > > I have a very narrow te

[sage-devel] Question about the sage venv.

I have a very narrow techical question. I am hoping for a narrow technical answer, preferably from someone who was involved in designing the Sage venv. QUESTION: Why doesn't the Sage venv contain a pyvenv.cfg file? When you read PEP 405 you learn that the

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I should also have mentioned that macOS is an example of a system which does not come with libjpeg. On Fri, Nov 17, 2023 at 12:53 PM Marc Culler wrote: > No, I meant both "normal" and "standard". I am sure I will master this > terminology sooner or later. > > On

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

No, I meant both "normal" and "standard". I am sure I will master this terminology sooner or later. On Friday, November 17, 2023 at 12:51:48 PM UTC-6 Marc Culler wrote: > I meant "normal" when I said "standard". > > On Friday, November 17, 20

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I meant "normal" when I said "standard". On Friday, November 17, 2023 at 12:49:18 PM UTC-6 Marc Culler wrote: > I expect to receive lots of flak for saying this, but I support making > libjpeg be a standard spkg using the source code from > https://libjpeg.s

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I expect to receive lots of flak for saying this, but I support making libjpeg be a standard spkg using the source code from https://libjpeg.sourceforge.net. I just built version jpeg-9e on Ubuntu 18.04 and macOS 10.13. The standard ./configure ; make install method works flawlessly - not

Re: [sage-devel] Cython errors when building p_group_cohomology

Thank you, Edgar! That worked. - Marc On Wednesday, November 15, 2023 at 7:15:45 PM UTC-6 Edgar Costa wrote: > Marc, you should try something like this: > https://github.com/edgarcosta/pyfib/commit/f30cd702f5b8610a284b1b1f425ef22b2a2a11fa > > On Wed, Nov 15, 2023 at 6:49 PM Marc C

[sage-devel] Cython errors when building p_group_cohomology

I am not able to build the optional package p_group_cohomology in 10.2.rc2 due to cython errors. The first error looks like: [p_group_cohomology-3.3.3.p1] Error compiling Cython file: [p_group_cohomology-3.3.3.p1] --- -

Re: [sage-devel] Symengine package fails to build in 10.2rc2

I see your unanswered message "ping" on issue #456 from 5 days ago. But in the Releases section I see that v0.11.0 was released 2 days ago. - Marc On Tuesday, November 14, 2023 at 11:50:55 AM UTC-6 Dima Pasechnik wrote: > On Tue, Nov 14, 2023 at 5:18 PM Marc

Re: [sage-devel] Re: Question about make dependencies

installed. > > On Tuesday, November 14, 2023 at 9:37:09 AM UTC-8 Marc Culler wrote: > >> For me, one of the most frustrating parts of building sage is that, >> whenever a build fails, the make system decides that gmp is out of date and >> hence I have to wait fo

Re: [sage-devel] Re: Question about make dependencies

I was hesitant to send that message because I didn't want to have to go through this again. On Tue, Nov 14, 2023 at 11:58 AM Dima Pasechnik wrote: > > Does ./configure say why the system copy is unsuitable? > There is no system copy. I imagine it might be an artifact of the design of Sage on

[sage-devel] Re: Question about make dependencies

On Tuesday, November 14, 2023 at 11:37:09 AM UTC-6 Marc Culler wrote: > For me, one of the most frustrating parts of building sage is that, > whenever a build fails, the make system decides that gmp is out of date and > hence I have to wait for it to recompile gmp and all of its dep

[sage-devel] Question about make dependencies

For me, one of the most frustrating parts of building sage is that, whenever a build fails, the make system decides that gmp is out of date and hence I have to wait for it to recompile gmp and all of its dependencies. Is this intentional? Does anyone know why it happens? Is it avoidable? Or

[sage-devel] Symengine package fails to build in 10.2rc2

The symengine package has apparently not been updated to be compatible with cython 3. This is what I see in the log (full log attached): performance hint:

Re: [sage-devel] Question about reading Sage documentation

is no, or not easily. I thought that topic might be pertinent here. - Marc On Thu, Jun 29, 2023 at 6:48 PM Michael Orlitzky wrote: > On 2023-06-29 14:46:00, Marc Culler wrote: > > During our recent release of SnapPy we ran across an issue which is > likely > > relevant

[sage-devel] Re: Voting: Block-scoped optional tag and the keyword

I vote for (C). On Wednesday, June 28, 2023 at 9:40:07 PM UTC-5 Kwankyu Lee wrote: > Hi, > > We spent six days for the preliminary discussion in the sage-devel thread > > https://groups.google.com/g/sage-devel/c/OUnoroIf0qc > > about choosing the keyword triggering block-scoped optional tag

[sage-devel] Question about reading Sage documentation

During our recent release of SnapPy we ran across an issue which is likely relevant to whether Sage's documentation is viewable on newer Ubuntu systems (such as 22.04). The issue is that these newer Ubuntu systems ship Firefox as a snap. A snap runs in a sandbox which restricts which files

Re: [sage-devel] Graphics files in Sage documentation

Right. That is what I will be doing. - Marc On Wed, Jun 28, 2023, 5:27 PM Dima Pasechnik wrote: > One can always start a web server on localhost, instead of using file:/// > :P > > On Wed, Jun 28, 2023 at 11:16 PM Michael Orlitzky > wrote: > > > > On Wed, 2023-06-28 at 13:50 -0400, Michael

Re: [sage-devel] Graphics files in Sage documentation

;> >> # We do *not* fully initialize intersphinx since we call it by hand >> # in find_sage_dangling_links. >> >> >> (I'm not suggesting this as a general change, just for your particular >> situation.) >> >> >> On Wednesday, June 28, 2023 at

Re: [sage-devel] Graphics files in Sage documentation

.svg local/share/doc/sage/html/en/reference/manifolds/sage/manifolds/chart-12.png local/share/doc/sage/html/en/reference/manifolds/sage/manifolds/chart-12.pdf - Marc On Wednesday, June 28, 2023 at 2:02:47 PM UTC-5 Marc Culler wrote: > I think I may have found a resolution of this prob

Re: [sage-devel] Graphics files in Sage documentation

/sage/manifolds/chart.html: Since this seems to be a change between 10.1beta3 and 10.1beta4, I would have to guess that it might be considered a bug. So maybe I should move this back to sage-release? - Marc On Wednesday, June 28, 2023 at 1:13:20 PM UTC-5 Marc Culler wrote: > I

Re: [sage-devel] Graphics files in Sage documentation

3-06-28 at 10:07 -0700, Marc Culler wrote: > > > > BOTTOM LINE: we get more than a 90% reduction in size simply by choosing > to > > use the .svg extension when saving the plot instead of the .png > extension. > > > > SVG is the right choice for most

[sage-devel] Graphics files in Sage documentation

At John Palmieri's suggestion, I am duplicating this message that I posted on sage-release on this list: Details really do matter. The devil is in them. Here is one which makes a major difference to my efforts to distribute Sage. I hope that I can convince people to pay attention to it.

Re: [sage-devel] ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

On Tuesday, May 30, 2023 at 9:17:17 AM UTC-5 Dima Pasechnik wrote: Well, have you notiiced that while casting his vote, Matthias wrote a full screenful of questionable explanations of why he voted "no", That is what always happens when people try to force a vote before there has been a

[sage-devel] Re: Trac #34152 needs you (to vote)!

If I am allowed to vote, my vote is hybrid > copy files > pseudo package. - Marc On Tuesday, August 23, 2022 at 6:38:40 PM UTC-5 François Bissey wrote: > Hi all, > > https://trac.sagemath.org/ticket/34152 needs help to decide what solution > we implement going forward. > > The ticket is

[sage-devel] Re: Proposal: downgrade some packages to experimental

Incidentally, the patch for p_group_cohomology that I uploaded above also appeared in #30787 <https://trac.sagemath.org/ticket/30787> . <https://trac.sagemath.org/query?status=needs_work> - Marc On Sunday, August 7, 2022 at 7:49:41 AM UTC-5 Marc Culler wrote: > The p_group_coh

[sage-devel] Re: Proposal: downgrade some packages to experimental

Yes, there is a ticket for this. It is #34221 . The current version of Cython ignores .pxd files in directories with no __init__.py. The ticket backports a cython fix for that problem which will appear in a future Cython release. - Marc On Saturday,

[sage-devel] Re: Proposal: downgrade some packages to experimental

The p_group_cohomology package is included in the macOS binary release. it requires a patch to its spkg-install,sh. Symengine_py is also included in the macOS binary and also needs a patch. I am attaching a tarball of the build/pkg directories for those two packages. - Marc On Sunday,

Re: [sage-devel] Re: Sage 9.7 Doctest/Install Error Sage9.6 Crash Report

I just verified that the bug reported in trac #33212 does not arise with the current prerelease of the binary SageMath 9.7 app, which is based on 9.7.beta5. This is consistent with the trac report since the app is built with XCode 13.3.1. Note that the binary app will work on older versions

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

Hi Matthias, I have one correction to the 9.6 installation manual. There are no longer two choices for the macOS binary installation. There is exactly one choice: a 1GB download which includes every optional package that we were able to build, except for those which can be installed with the

[sage-devel] Sage binary for macOS

A prelease version of the macOS Sagemath app based on Sage 9.6.rc0 has been available on github for about a week now. I am writing to ask people with Apple computers to test the app and report problems as github issues. So far there have

[sage-devel] The symengine spkg tries to install in /usr/local

When trying to build 9.6.rc0 for the macOS app I got a failure when installing the symengine package. The error was: Install the project... -- Install configuration: "Release" CMake Error at cmake_install.cmake:41 (file): file cannot create directory: /usr/local/lib/cmake/symengine. Maybe

Re: [sage-devel] Failure to build Sage 9.4 on Monterey

The binary release of SageMath 9.4 for Intel Macs is reported to work fine with Rosetta. - Marc On Friday, January 28, 2022 at 3:12:29 PM UTC-6 dim...@gmail.com wrote: > 9.4 is not known to run on M1. > Try the latest, 9.5.rc4, instead. > > On Fri, 28 Jan 2022, 19:03 Jeremy Martin, wrote: >

Re: [sage-devel] Re: upgrade sagecell (http -> https)

It is not a good idea to use a self-signed certificate since most browsers will refuse to connect or require extra steps to do so. A much better approach is to use a certbot certificate, which is free, convenient and accepted by most if not all browsers. On Friday,

Re: [sage-devel] Re: python3-3.9.2 failed to build while running 'sage -i pynormaliz' (ModuleNotFoundError: No module named 'binascii')

On Thu, Jun 24, 2021 at 11:50 AM Dima Pasechnik wrote: > > There is no need to build Python, you can either use one from Homebrew > or from the official Python distribution. > That is an extremely unhelpful answer, especially given what I am trying to do. It is also ridiculous. If people are