Re: [sage-devel] Re: Just Crazy

They are not exactly entry points, since they are not advertised in the package metadata since there is no package metadata since there is no package (yet). I don't understand what you mean with this sentence. There is a sagemath package, defined in the pyproject.toml file in the root, whose

Re: [sage-devel] Re: Just Crazy

On Wednesday, October 1, 2025 at 7:20:28 PM UTC-5 dim...@gmail.com wrote: . Why did you assume that venv/bin/sage is what ./sage is using? You are right that I have been making some assumptions. Not that venv/bin/sage is what the so-called "./sage" is using; not even that venv/bin/sage and

Re: [sage-devel] Re: Just Crazy

On Wed, Oct 1, 2025 at 12:13 PM Marc Culler wrote: > Sure. The main point is that this change is a breaking change and it was > made with no general discussion and no warning. (No doubt there was some > discussion in the PR, but that is not really the same thing.) > I agree that this change sh

Re: [sage-devel] Re: Just Crazy

On Wed, Oct 1, 2025 at 4:27 PM Dima Pasechnik wrote: > To summarise, nothing is "Crazy" here, from sage the distro point of view. > Nobody said anything was crazy from the "sage the distro point of view". Nor did anyone say that these changes made things worse. I did say it is "crazy" to make b

Re: [sage-devel] Re: Just Crazy

To summarise, nothing is "Crazy" here, from sage the distro point of view. Internal scripts in venv/ are not what they used to be, but they were never intended for direct public consumption. It's true though that several scripts in src/bin/ are overdue for maintenance. In particular I can take ca

Re: [sage-devel] Re: Just Crazy

El miércoles, 1 de octubre de 2025 a las 17:47:02 UTC+2, David Roe escribió: I'm having trouble figuring out where this change was introduced. The folder sage/venv doesn't exist in the repo, so presumably sage/venv/bin/sage is copied from elsewhere during the build process, but I wasn't able t

Re: [sage-devel] Re: Just Crazy

El miércoles, 1 de octubre de 2025 a las 20:23:49 UTC+2, David Roe escribió: 2. Identify the backward incompatible changes in #39030 (and elsewhere, such as #39015 ). At some point, the public interface

Re: [sage-devel] Re: Just Crazy

On Wed, Oct 1, 2025 at 3:55 PM Dima Pasechnik wrote: > > I am sorry, what does make you think that `./sage --python` is removed? > Looking at the argument parser defined in the cli folder , I don't see --python added anywhere, so I woul

Re: [sage-devel] Re: Just Crazy

I am sorry, what does make you think that `./sage --python` is removed? Are you talking about an internal script? If so, it's certainly a fair game to change, it's not something user-facing, or something that's used by many developers. $ ./sage ┌

[sage-devel] Python, the movie! The programming language’s origin story comes to the silver screen

https://www.nature.com/articles/d41586-025-02903-1 I thought this might be of interest to some in this list. John -- 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

Re: [sage-devel] Re: Just Crazy

Another useful option which got removed is --python. It is sometimes useful to be able to check if something works in the same python that sage runs in, and it is not necessarily obvious which one that is when there are multiple versions of python installed. Even on linux it is possible to ha

Re: [sage-devel] Re: Just Crazy

On 2025-10-01 14:23:31, David Roe wrote: > 2. Identify the backward incompatible changes in #39030 > (and elsewhere, such as #39015 > ). At some point, the public > interface to the sage script consisted of

Re: [sage-devel] Re: Just Crazy

Thanks Marc, that helps a lot. Looking at the cli folder , it only supports a small fraction of the command line options of the old bash script. Personally, I think this model is a lot better and more maintainable, but we sho

Re: [sage-devel] Re: Just Crazy

> > Marc's answer about pyproject.toml still doesn't tell me where to find > the Python code that's actually being run when you type sage. > It runs the code in the file sage/venv/bin/sage, which is an entry point generated automatically by the build system. That file contains the following (whe

Re: [sage-devel] Re: Just Crazy

Indeed, the change from the bash script to the new python script is pretty well obfuscated. The old bash script still exists as src/bin/sage but it is not used. To see where the new python replacement gets created you have to look inside the file sage/pyproject.toml. There you find: [project

Re: [sage-devel] Re: Just Crazy

Sure. The main point is that this change is a breaking change and it was made with no general discussion and no warning. (No doubt there was some discussion in the PR, but that is not really the same thing.) David, there is no venv directory in the source. It is a symlink created during the

Re: [sage-devel] Re: Sage development norms and procedures

No, no autocratic decisions. The authority of the community to do various unpleasant plumbing and swamp draining on the system is, de facto, delegated to whoever volunteers to get their hands dirty. The community normally appreciates the work done, and tolerates minor hiccups which always aris

Re: [sage-devel] Re: Just Crazy

I'm having trouble figuring out where this change was introduced. The folder sage/venv doesn't exist in the repo, so presumably sage/venv/bin/sage is copied from elsewhere during the build process, but I wasn't able to figure out where in a few minutes of poking around. Similarly, I don't see any

[sage-devel] Re: Just Crazy

This is regarding the options which were eliminated in the new stealth-replaced backwards-incompatible sage executable. One important option which was very useful to me, and which is now gone, allowed specifying the directory where notebooks are stored: usage: sage [-h] [-v] [-q] [--simple-pro

[sage-devel] Just Crazy

After finally getting Sage 10.8beta5 to build in the context which I need for the Sage_macOS app, I built the app, only to find that it is completely broken. The reason turns out to be that the main sage executable (sage/venv/bin/sage) has completely changed. The long bash script which parses