On Sat, 2022-01-08 at 23:27 -0800, Jonathan Thornburg wrote:
> what's the idiomatic way for some other piece of Sage source code to
> execute the contents of all of those files? What I've been doing is
> to create another file (say 'setup.sage') which contains the lines
> load('foo.sage')
> lo
I wrote:
> I've noticed that some (many) Python-level error messages (e.g., syntax
> errors) from Sage 9.5.beta8 fail to give the name of the source file
> in which the error occured. [[...]]
On Sat, Jan 08, 2022 at 10:24:07PM -0500, Michael Orlitzky replied:
> I think the load() method has been
On 2022-01-08 18:56:21, Jonathan Thornburg wrote:
> I've noticed that some (many) Python-level error messages (e.g., syntax
> errors) from Sage 9.5.beta8 fail to give the name of the source file
> in which the error occured. For example, a few minutes ago I got this
> error message from a Sage cod
I've noticed that some (many) Python-level error messages (e.g., syntax
errors) from Sage 9.5.beta8 fail to give the name of the source file
in which the error occured. For example, a few minutes ago I got this
error message from a Sage code I'm working on:
> Traceback (most recent call last):
>
