Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

On Friday, December 9, 2016 at 10:13:03 PM UTC, Bill Hart wrote: > > Ah I see. I assumed it would also try to spawn a browser or something. > the default ( notebook()) is indeed to try to open a browser/browser tab to show the URL served by the server, whereas notebook(automatic_login=False)

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

Ah I see. I assumed it would also try to spawn a browser or something. On the other hand, I understand some of the networking stuff is still not completed. You can of course use wget and the like so it can't be too broken. Bill. On Friday, 9 December 2016 15:15:43 UTC+1, Dima Pasechnik wrote:

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

On Wed, Dec 07, 2016 at 02:50:15PM +, Tobias Hansen wrote: > On 12/07/2016 01:26 PM, Jeroen Demeyer wrote: > If you look at the patch [1] that was applied, there is a new check for > tp_new(). I'm not 100% sure that's what causes the problem, but it looks > suspicious. > > [1]

Re: [sage-devel] Re: Python Debugging / Using PUDB with Sage

I didn't do much with setting traces / breakpoints from within the Python code itself in the tutorial. You can call from pudb import set_trace as bp; bp() to launch the pudb debugger at a certain point in the code. This should simplify having to manually add all of the breakpoints from within the

[sage-devel] Re: Python Debugging / Using PUDB with Sage

On Friday, December 9, 2016 at 4:07:18 PM UTC, Maxie Schmidt wrote: > > For the sake of completeness, I'm adding a link to a SMC wiki tutorial on > using PUDB with Sage (for both local source installs and within the SMC > terminal application): > >

Re: [sage-devel] Re: Python Debugging / Using PUDB with Sage

And if you do "sage -sh" first, then it'll use a different pudb installed into sage. (sorry for spamming the list) On Fri, Dec 9, 2016 at 10:19 AM, William Stein wrote: > Also, pudb is now pre-installed systemwide so `pip install pudb` is no > longer needed > > On Fri, Dec

Re: [sage-devel] Re: Python Debugging / Using PUDB with Sage

Also, pudb is now pre-installed systemwide so `pip install pudb` is no longer needed On Fri, Dec 9, 2016 at 10:16 AM, William Stein wrote: > On Fri, Dec 9, 2016 at 9:58 AM, William Stein wrote: >> On Fri, Dec 9, 2016 at 8:07 AM, Maxie Schmidt

Re: [sage-devel] Re: Python Debugging / Using PUDB with Sage

On Fri, Dec 9, 2016 at 8:07 AM, Maxie Schmidt wrote: > For the sake of completeness, I'm adding a link to a SMC wiki tutorial on > using PUDB with Sage (for both local source installs and within the SMC > terminal application): >

[sage-devel] Re: Python Debugging / Using PUDB with Sage

For the sake of completeness, I'm adding a link to a SMC wiki tutorial on using PUDB with Sage (for both local source installs and within the SMC terminal application): https://github.com/sagemathinc/smc/wiki/Using-a-GUI-Python-Debugger-with-Sage-(PUDB). Maxie On Tuesday, November 29, 2016

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

On Friday, December 9, 2016 at 12:48:30 PM UTC, Bill Hart wrote: > > The Sage Notebook isn't likely to work under the WSL. It's a text console > environment only. Microsoft intended it mainly to provide Linux development > tools to people, not as a way of running graphical applications. >

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

The Sage Notebook isn't likely to work under the WSL. It's a text console environment only. Microsoft intended it mainly to provide Linux development tools to people, not as a way of running graphical applications. You can probably fix the memory allocation issues though. You likely need to

[sage-devel] Re: inconsistent Sagemath doc licenses - a fix is needed

On Friday, December 9, 2016 at 8:28:35 AM UTC, mmarco wrote: > > I am not so sure about that. Is it safe to assume that the author of a > file that clearly states to be under the GPL is also giving permission to > release a derivative work under a dual license? > By adding the code to Sage

[sage-devel] Re: inconsistent Sagemath doc licenses - a fix is needed

I am not so sure about that. Is it safe to assume that the author of a file that clearly states to be under the GPL is also giving permission to release a derivative work under a dual license? El jueves, 8 de diciembre de 2016, 21:52:07 (UTC+1), Dima Pasechnik escribió: > > > > On Thursday,