Re: [sage-devel] Re: load deprecation warning in SageCell

On Sat, 10 Sep 2022, 10:01 Mike, wrote: > The sage cell server I'm using is sagecell.sagemath.org. Is there > someone I should ask to apply that patch? > the main contact for this sagecell is listed there on the 1st page, at the Problems section near the bottom. > On Wednesday, September 7,

Re: [sage-devel] Re: load deprecation warning in SageCell

The sage cell server I'm using is sagecell.sagemath.org. Is there someone I should ask to apply that patch? On Wednesday, September 7, 2022 at 4:23:37 PM UTC-4 dim...@gmail.com wrote: > On Wed, Sep 7, 2022 at 9:14 PM Mike wrote: > > > > Since the referenced fix won't be available until sage-9.

[sage-devel] Re: load deprecation warning in SageCell

Thank you for the suggestion, but I'd rather change the cell content as little as possible. I'm trying to present a simple interface to my freshmen students, so I think it'll be easier to tell them to ignore the warnings than to explain the extra code. (I was hoping the load command might have

[sage-devel] Re: load deprecation warning in SageCell

On Tuesday, 24 May 2022 at 11:10:13 UTC-7 ingo...@gmail.com wrote: > When I call > *load('https://raw.githubusercontent.com/ingodahn/sageutils/master/physics.py > ')* > in a sagecell I get in the output > */home/sc_serv/sage/

Re: [sage-devel] Re: load deprecation warning in SageCell

On Wed, Sep 7, 2022 at 9:14 PM Mike wrote: > > Since the referenced fix won't be available until sage-9.7, is there a > (temporary) way to avoid this error message when loading files from github > into a sage cell? you basically need to apply the patch from https://trac.sagemath.org/ticket/33771

[sage-devel] Re: load deprecation warning in SageCell

Since the referenced fix won't be available until sage-9.7, is there a (temporary) way to avoid this error message when loading files from github into a sage cell? On Tuesday, May 24, 2022 at 3:02:51 PM UTC-4 Matthias Koeppe wrote: > Fixed in https://trac.sagemath.org/ticket/33771 > > On Tuesda

[sage-devel] Re: load deprecation warning in SageCell

Fixed in https://trac.sagemath.org/ticket/33771 On Tuesday, May 24, 2022 at 11:10:13 AM UTC-7 ingo...@gmail.com wrote: > When I call > *load('https://raw.githubusercontent.com/ingodahn/sageutils/master/physics.py > ')* > in

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Thursday, 4 April 2019 09:48:58 UTC+3, Yagamy Light wrote: > > > > On Thursday, 4 April 2019 03:21:22 UTC+3, John H Palmieri wrote: >> >> >> >> On Wednesday, April 3, 2019 at 4:20:43 PM UTC-7, Yagamy Light wrote: >>> >>> >>> >>> On Thursday, 4 April 2019 01:58:09 UTC+3, John H Palmieri wrote:

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Thursday, 4 April 2019 03:21:22 UTC+3, John H Palmieri wrote: > > > > On Wednesday, April 3, 2019 at 4:20:43 PM UTC-7, Yagamy Light wrote: >> >> >> >> On Thursday, 4 April 2019 01:58:09 UTC+3, John H Palmieri wrote: >>> >>> >>> >>> On Wednesday, April 3, 2019 at 3:13:43 PM UTC-7, Yagamy Light

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Wednesday, April 3, 2019 at 4:20:43 PM UTC-7, Yagamy Light wrote: > > > > On Thursday, 4 April 2019 01:58:09 UTC+3, John H Palmieri wrote: >> >> >> >> On Wednesday, April 3, 2019 at 3:13:43 PM UTC-7, Yagamy Light wrote: >>> >>> >>> >>> On Wednesday, 3 April 2019 22:42:15 UTC+3, Samuel Lelievre

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Thursday, 4 April 2019 01:58:09 UTC+3, John H Palmieri wrote: > > > > On Wednesday, April 3, 2019 at 3:13:43 PM UTC-7, Yagamy Light wrote: >> >> >> >> On Wednesday, 3 April 2019 22:42:15 UTC+3, Samuel Lelievre wrote: >>> >>> >>> >>> Le mercredi 3 avril 2019 17:43:51 UTC+2, Yagamy Light a écrit

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Wednesday, April 3, 2019 at 3:13:43 PM UTC-7, Yagamy Light wrote: > > > > On Wednesday, 3 April 2019 22:42:15 UTC+3, Samuel Lelievre wrote: >> >> >> >> Le mercredi 3 avril 2019 17:43:51 UTC+2, Yagamy Light a écrit : >>> >>> # Steps to reproduce (in terms of terminal comands: >>> >>> $ cat

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Wednesday, 3 April 2019 22:42:15 UTC+3, Samuel Lelievre wrote: > > > > Le mercredi 3 avril 2019 17:43:51 UTC+2, Yagamy Light a écrit : >> >> # Steps to reproduce (in terms of terminal comands: >> >> $ cat sagemath_test.sage >> plot(graphs.HeawoodGraph()) >> $ sage >> ┌─

[sage-devel] Re: load() function doesn't pop up a PNG viewer

Le mercredi 3 avril 2019 17:43:51 UTC+2, Yagamy Light a écrit : > > # Steps to reproduce (in terms of terminal comands: > > $ cat sagemath_test.sage > plot(graphs.HeawoodGraph()) > $ sage > ┌┐ > │ SageMath ver

[sage-devel] Re: %load

On 3/24/14, 3:25, Volker Braun wrote: I find the various commands to evaluate code from a file confusing (and not really documented). When was the English language changed so that "load" implies evaluation? Probably when it was programmed into magma: http://linux.math.tifr.res.in/manuals/html/

[sage-devel] Re: %load

Hi Volker, On 2014-03-24, Volker Braun wrote: > IMHO we should have > > %load # as provided by ipython > %run # evaluate file content, preparsed depending on the file > extension > %attach # like run, but watch for changes Sounds good to me. -- You received this message because you

[sage-devel] Re: %load

I find the various commands to evaluate code from a file confusing (and not really documented). When was the English language changed so that "load" implies evaluation? Also, changing the way IPython works is only going to confuse me more, not less. IMHO we should have %load # as provided

[sage-devel] Re: %load

Hi William, >> > On Sun, Mar 23, 2014 at 3:36 PM, William Stein wrote: >> >> >> >> Hi, >> >> >> >> In Sage 0.0 - 5.12, I could create a file foo.sage and type >> >> >> >> sage: load foo.sage # or %load foo.sage >> >> >> >> and evaluate its contents. In sage-6.2(beta) I get some interactive >

[sage-devel] Re: %load

On Sun, Mar 23, 2014 at 3:36 PM, William Stein wrote: > Hi, > > In Sage 0.0 - 5.12, I could create a file foo.sage and type > > sage: load foo.sage # or %load foo.sage > > and evaluate its contents. In sage-6.2(beta) I get some interactive I better add that this is Sage-6.2 beta along with I

[sage-devel] Re: load/attach bugs

There is no need to put in a long description within the patch: just put in a short one and add detail on the trac ticket. And you can use whatever editor you like. For me hg pops up emacs, presumably because I have environment variable set to "emacs -nw" John 2009/4/27 Rado : > > Alright, her

[sage-devel] Re: load/attach bugs

On Sun, Apr 26, 2009 at 5:59 PM, Rado wrote: > > Alright, here is my first open-source project patch: > > http://www.math.uiuc.edu/~rkirov2/sage/11803.patch Thanks. I've posted the patch here: http://trac.sagemath.org/sage_trac/ticket/5908 > > The description in the patch file is short becaus

[sage-devel] Re: load/attach bugs

Alright, here is my first open-source project patch: http://www.math.uiuc.edu/~rkirov2/sage/11803.patch The description in the patch file is short because vi is driving me insane. I was going to add a better description in the .patch file with gedit but wasn't sure if it is checksumed. Here is m

[sage-devel] Re: load/attach bugs

On Sat, Apr 25, 2009 at 4:30 PM, Rado wrote: > > Sweet, I will give it a shot. > > One last thing I noticed is that attached_files() is not exposed to > the user. Again not sure if this is how its supposed to work or an > actual bug. But if one can attach without refering to a library it > would

[sage-devel] Re: load/attach bugs

Sweet, I will give it a shot. One last thing I noticed is that attached_files() is not exposed to the user. Again not sure if this is how its supposed to work or an actual bug. But if one can attach without refering to a library it would make sense to see what is currently attached again without

[sage-devel] Re: load/attach bugs

On Fri, Apr 24, 2009 at 9:07 PM, Rado wrote: > > Alright I got how to make ``load "test space.py"`` work for the > notebook too. The problem is in: > > /home/rado/sage-3.4/devel/sage/sage/server/notebook/worksheet.py > > line 3558:  for filename in L.split(): > > the python split function splits

[sage-devel] Re: load/attach bugs

Alright I got how to make ``load "test space.py"`` work for the notebook too. The problem is in: /home/rado/sage-3.4/devel/sage/sage/server/notebook/worksheet.py line 3558: for filename in L.split(): the python split function splits "test space.py" to '"test' and 'space.py"'. I googled for a b

[sage-devel] Re: load/attach bugs

> I can fix 2) at $SAGE_ROOT/devel/sage/sage/misc/interpreter.py > but actually I need a fix for 1) since I keep my files with folders > with spaces. Since prompt works with files with spaces, it shouldn't > be too hard to make the notebook work with those too, right?!? Curiously the notebook han

[sage-devel] Re: load/attach bugs

I think I worded myself badly in the previous post. I see now that its a design decision to use this syntax USAGE: ``attach file1 file2 ...`` - space-separated list of .py, .spyx, and .sage files. instead of ``attach file1 arguments`` (this is the ipython syntax). You are right obviously

[sage-devel] Re: load/attach bugs

>> (a file to take arguments from command line) /home/rado/.sage/ >> testarg.py This is not what load/attach were intended for (and why do you expect it to work?), but it's not a terrible idea. Certainly attach should never support passing arguments, that's just perverse. Nick --~--~--

[sage-devel] Re: load/attach bugs

On Apr 24, 6:24 pm, Rado wrote: > Hello, Hi Rado, > I was trying to load some python files and found some weird behaviour > of the load/attach commands. I have three test files > > (a normal file) /home/rado/.sage/test.py > (a file with space in the name) /home/rado/.sage/test space.py > (a f