Re: [sage-devel] Developing in general

On Mon, 25 Jan 2016, Jeroen Demeyer wrote: But numbers 2-1 does not seem so strong base for decision. Sure, but that is because it is such a specific question about Posets. True. But there have been some more general discussions, and I think that even those have not had that many people. I

[sage-devel] Conversion Jupyter Notebook -> Doctests

Is there a way to convert a jupyter notebook .ipynb to a "doctestable file"? Such a thing existed for the sage notebook. I would like to have that for two reasons: - once I am satisfied with computations in a notebook for a paper, I'd like to convert it and run doctests on it (e.g., with later ver

Re: [sage-devel] Jupyter notebook by default?

On Tuesday, January 26, 2016, kcrisman wrote: > > >> >> For what it is worth, SageMathCloud has a buttons/lists, etc. for >> editing markdown in Sage worksheets, and also a realtime preview >> markdown editor for md files. Two screenshots attached. I also fully >> implemented a realtime WYSIWYG

Re: [sage-devel] Re: Jupyter notebook by default?

> Oh yeah, I forgot that I get very confused trying to make text cells in > SMC too :( presumably for the same reason that I don't want to type %md - > but I don't use SMC much (yet). > (I.e. this might be awesome after all but I haven't gotten that far!) -- You received this message beca

Re: [sage-devel] Re: Jupyter notebook by default?

> > For what it is worth, SageMathCloud has a buttons/lists, etc. for > editing markdown in Sage worksheets, and also a realtime preview > markdown editor for md files. Two screenshots attached. I also fully > implemented a realtime WYSIWYG editor for html and markdown a year > ago, but de

Re: [sage-devel] Re: Jupyter notebook by default?

Jason, thanks for your quick replies, very informative. What if we used something like ProseMirror for the markdown editor? >> http://prosemirror.net/ >> . >> >> Would that help? Ri

Re: [sage-devel] Re: Jupyter notebook by default?

I should add that one of the major design goals for the next iteration of the notebook is to be fully modular, so it would be easy to plug in your own component to edit markdown, for example. Thanks, Jason On Tue, Jan 26, 2016 at 10:59 PM Jason Grout wrote: > What if we used something like Pro

Re: [sage-devel] Re: Jupyter notebook by default?

What if we used something like ProseMirror for the markdown editor? http://prosemirror.net/. Would that help? Right now we use Codemirror. I'm writing a prototype for the next Jupyter notebook renderer as we speak (markdown cells are here, for example: https://github.com/jupyter/jupyter-js-cells/

[sage-devel] Re: Jupyter notebook by default?

Another con I just discovered: * You have to learn markdown to do anything useful in plain old text. Don't tell me this isn't a con. (If it's not accurate, please tell me! I just couldn't figure out how to get Now, I know enough md to get by. Lots of people use it. Lots of *other* people

[sage-devel] Re: Getting Started

I second that. In addition, the "Ticket reports" page at http://trac.sagemath.org/wiki/TicketReports has a link to "beginner" tickets which are good tickets to get started with our development process. The content of these tickets is easy (sometimes just a typo), so you focus on the developme

Re: [sage-devel] Hacker news thread about math software ("Announcing Wolfram Programming Lab")

I think it is somewhat disheartening to see Mathematica accepted as a program whose major or only flaw is that it is not open source. But maybe I didn't read all the comments. It seems that the ycombinator contributors tend to rattle on a while. RjF On Wednesday, January 20, 2016 at 5:49:13 AM

Re: [sage-devel] Re: Hm, seemingly wrong bracketing works anyway?

On Tue, Jan 26, 2016 at 12:40 PM, Eric Gourgoulhon wrote: > Quite surprising! > Indeed, one has > > sage: preparse("[1..len(a])") > '(ellipsis_range(Integer(1),Ellipsis,len(a)))' > > So the culprit seems to be sage preparser. The preparser barely "parses" -- it just does some transformations befo

[sage-devel] Re: Hm, seemingly wrong bracketing works anyway?

Quite surprising! Indeed, one has sage: preparse("[1..len(a])") '(ellipsis_range(Integer(1),Ellipsis,len(a)))' So the culprit seems to be sage preparser. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop re

[sage-devel] Hm, seemingly wrong bracketing works anyway?

Is it just me finding it wired that the following works with the wrong bracketing [1..len(a]) ? sage: a = [1,2,3] sage: [1..len(a]) [1, 2, 3] Cheers, Christian -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] Re: Plots in plot.py documentation

Hi, new two problems. 1) GraphicsArray does not have a plot() method, so I added one in my local copy and everything went ok on examples like show(graphics_array([g1, g2], 2, 1), xmin=0) Is it ok to include the patch in this ticket or should I open a new one? 2) I cannot find a way to emulate g

[sage-devel] Re: jsmol broken on JupyterHub

It doesn't work right now; The kernel doesn't know whether it is running under jupyter or jupyterhub. On Tuesday, January 26, 2016 at 10:44:33 AM UTC-5, Christoph Ruegge wrote: > > Hi. > > I'm trying to get the jsmol applet running on JupyterHub. I'm using > JupyterHub 0.3.0 (installed via pip

[sage-devel] jsmol broken on JupyterHub

Hi. I'm trying to get the jsmol applet running on JupyterHub. I'm using JupyterHub 0.3.0 (installed via pip) and Sage 6.10. The applet works nicely in a locally running Jupyter, but inside JupyterHub, it fails. I tried to "jupyter nbextension install" jsmol, without success. I did some searchi

[sage-devel] Re: Matrix unicode output

> > help() with parameters to show longer help? (And smaller default than > help() now prints.) help() could definitely be more helpful on concepts. For instance, the typesetting we're talking about here could appear if you typed `help("terminal")` or something. There could be a list of predefine

[sage-devel] Re: Matrix unicode output

What about having an option at startup? Something like: sagestarts the command line interface with nice unicode sage -ascii starts the command line interface with the old style (for the user cases mentioned here: blind people, copy-paste able output and so on) El doming

[sage-devel] Re: Matrix unicode output

On Monday, January 25, 2016 at 8:42:45 PM UTC-5, Samuel Lelievre wrote: > > Type "%display unicode_art" for a nicer display of some outputs. > We know that this is ugly but if you dig into the documentation you'll be able to find better-looking settings, promise! -- You received this messag

[sage-devel] Re: Getting Started

As I see no other answers I volunteer mine. As a newbie myself in the developers community (two year user only) I began with tickets on documentation and graphics since it seemed to me the easiest way to get used to the development cycle and the inners of Sage programming slowly. You can either

[sage-devel] Re: Random doctest error in real_double.pyx

This is now http://trac.sagemath.org/ticket/19962 Le lundi 25 janvier 2016 15:19:31 UTC+1, Volker Braun a écrit : > > I've seen random test error there, too. +1 to removing them. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] Plots in plot.py documentation

There is a long discussion on this here http://trac.sagemath.org/ticket/17498 the original ticket which created the ::PLOT/sphinx_plot possibility. El lunes, 25 de enero de 2016, 21:24:58 (UTC+1), Jeroen Demeyer escribió: > > I'm sure there is probably a good reason, but why don't we just displa

Re: [sage-devel] Re: Matrix unicode output

On Tue, 26 Jan 2016, Daniel Krenn wrote: "Tip of the day"? Special command "hints()"? Essentially +1 for "hints()". However, help() seems to do a similar thing and maybe the FAQs above should go there? (FWIW, its now the first time I've looked at it; I would have looked at hints() probably ear

Re: [sage-devel] Re: Matrix unicode output

On 2016-01-26 06:58, Jori Mäntysalo wrote: > On Mon, 25 Jan 2016, Samuel Lelievre wrote: > >> When starting the Sage REPL, we currently display the following advice: >> >> Type "notebook()" for the browser-based notebook interface. >> Type "help()" for help. >> >> We could add a few more h

Re: [sage-devel] Re: Developing in general

On Mon, 25 Jan 2016, Volker Braun wrote: Examples of not "getting" code review from this thread: * At review of some small addition we start a general discussions about what Poset should do and then everybody votes on that  * Dislike of change/design pattern/author/..., hence I'm not reviewing t