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

2016-01-26 Thread jhonrubia6
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 display 
> all plots in the documentation? 
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread Eric Gourgoulhon
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 from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread kcrisman
 

>
> 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 decided it wasn't up to my standards (getting realtime sync 
> to fully work well was surprisingly challenging), so I 
> disabled/removed it.   
>

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'm surprised that there isn't more stuff out 
there trying to do fully-featured wysiwyg md editing, actually, obviously 
it is completely orthogonal to the math and of very general interest.  Huh.

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread kcrisman


> 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 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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread Jason Grout
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 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/blob/master/src/widget.ts#L110).
> Pull requests welcome, as always :).
>
> Jason
>
>
> On Tue, Jan 26, 2016 at 10:55 PM kcrisman  wrote:
>
>> 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 (see, I used it!) would rather have at least SOME whizzy-wig
>> capability.  'Cuz why else does the interface I'm using right now in Google
>> Groups have things *like this or **this* or even bullet lists to click
>> (perhaps they use TinyMCE themselves)?  It should be just as much about
>> reducing learning curves as the "right" solution.  I hate having to
>> remember if links are [like this](url) or (this)[url] or even [url like
>> this] (oh wait, that's the Trac style).  Google lets me do this
>>  with a simple click.
>>
>> To be productive on this front and not just complain, I did a fair amount
>> of searching for wysiwyg or tinymce and jupyter and found almost nothing.
>> Could this be a replacement?  https://github.com/bollwyvl/nb-wysiwyg  I
>> also found this nice article
>> 
>> which (correctly) claims "Why is Markdown better? Well, it’s worth saying
>> that maybe it isn't. Mainly, it’s not actually a question of better or
>> worse, but of what’s in front of you and of who you are. A definitive
>> answer depends on the user and on that user’s goals and experience. These
>> Notebooks don't use Markdown because it's definitely better, but rather
>> because it's different and thus encourages users to think about their work
>> differently."  But not everyone, especially those instructors in a hurry,
>> have time to think about that on a first try.  If they end up writing a
>> book I hope they do!  But if they just want to make an example for class
>> it's a bit much.
>>
>> Hopefully Jupyter will be able to have an option to have wysiwyg
>> eventually, though I understand that might conflict with their design
>> goals. In which case their design goals are not really for
>> non-programmers.
>>
>> Practical example, lest someone think I'm beating up on a straw notebook
>> interface:
>> Someone makes an awesome 3d plot in Jupyter with vectors and parametric
>> things in red, blue, and green, labeling different things.  Now in the main
>> body of their text they want the same output, so they can talk about green
>> tangent vectors, blue normal vectors, and red curves, or something, in
>> those colors.  Lovely stuff.  They Google how to do this in md and get:
>>
>> http://stackoverflow.com/questions/19746350/how-does-one-change-color-in-markdown-cells-ipython-notebook
>> Result: the text stays all black for the presentation they have to do in
>> ten minutes.
>>
>> --
>> 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 sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Conversion Jupyter Notebook -> Doctests

2016-01-26 Thread Clemens Heuberger
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 versions of SageMath)
- diffs between various versions would be much easier than diffing the .ipynb 
file.

Thanks,

Clemens

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Developing in general

2016-01-26 Thread Jori Mäntysalo

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 am one of them who have 
nothing to say about larger structure of Sage.


--
Jori Mäntysalo


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

2016-01-26 Thread Jason Grout
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/blob/master/src/widget.ts#L110).
Pull requests welcome, as always :).

Jason


On Tue, Jan 26, 2016 at 10:55 PM kcrisman  wrote:

> 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 (see, I used it!) would rather have at least SOME whizzy-wig
> capability.  'Cuz why else does the interface I'm using right now in Google
> Groups have things *like this or **this* or even bullet lists to click
> (perhaps they use TinyMCE themselves)?  It should be just as much about
> reducing learning curves as the "right" solution.  I hate having to
> remember if links are [like this](url) or (this)[url] or even [url like
> this] (oh wait, that's the Trac style).  Google lets me do this
>  with a simple click.
>
> To be productive on this front and not just complain, I did a fair amount
> of searching for wysiwyg or tinymce and jupyter and found almost nothing.
> Could this be a replacement?  https://github.com/bollwyvl/nb-wysiwyg  I
> also found this nice article
> 
> which (correctly) claims "Why is Markdown better? Well, it’s worth saying
> that maybe it isn't. Mainly, it’s not actually a question of better or
> worse, but of what’s in front of you and of who you are. A definitive
> answer depends on the user and on that user’s goals and experience. These
> Notebooks don't use Markdown because it's definitely better, but rather
> because it's different and thus encourages users to think about their work
> differently."  But not everyone, especially those instructors in a hurry,
> have time to think about that on a first try.  If they end up writing a
> book I hope they do!  But if they just want to make an example for class
> it's a bit much.
>
> Hopefully Jupyter will be able to have an option to have wysiwyg
> eventually, though I understand that might conflict with their design
> goals. In which case their design goals are not really for
> non-programmers.
>
> Practical example, lest someone think I'm beating up on a straw notebook
> interface:
> Someone makes an awesome 3d plot in Jupyter with vectors and parametric
> things in red, blue, and green, labeling different things.  Now in the main
> body of their text they want the same output, so they can talk about green
> tangent vectors, blue normal vectors, and red curves, or something, in
> those colors.  Lovely stuff.  They Google how to do this in md and get:
>
> http://stackoverflow.com/questions/19746350/how-does-one-change-color-in-markdown-cells-ipython-notebook
> Result: the text stays all black for the presentation they have to do in
> ten minutes.
>
> --
> 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 sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread kcrisman
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? Right now we use Codemirror.
>>
>>
This seems like a step in the right direction.  We don't need "flawless" 
copying of TinyMCE, for instance, but no ability to do wysiwyg in the text 
cells would definitely be unfortunate for that market segment, as it were.  

This?  Even finding things between TinyMCE and md is 
http://leeoniya.github.io/reMarked.js/ 
 

> 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/blob/master/src/widget.ts#L110). 
>>  
>> Pull requests welcome, as always :).
>>
>> Jason
>>
>>>
>>>
 

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread William Stein
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 editor for html and markdown a year
>> ago, but decided it wasn't up to my standards (getting realtime sync
>> to fully work well was surprisingly challenging), so I
>> disabled/removed it.
>>
>
> 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'm surprised that there isn't more stuff
> out there trying to do fully-featured wysiwyg md editing, actually,
> obviously it is completely orthogonal to the math and of very general
> interest.  Huh.
>

I surprisingly don't remember even one user request for such
tinymce style wysiwyg editing for SMC.  And our users are constantly asking
for the functionality they feel they really need...  I'm very surprised by
this lack of demand. However maybe they don't know what they want.



>
>>
>>
>> --
> 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 sage-devel+unsubscr...@googlegroups.com
> 
> .
> To post to this group, send email to sage-devel@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my massive iPhone 6 plus.

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread kcrisman
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 (see, I used it!) would rather have at least SOME whizzy-wig 
capability.  'Cuz why else does the interface I'm using right now in Google 
Groups have things *like this or **this* or even bullet lists to click 
(perhaps they use TinyMCE themselves)?  It should be just as much about 
reducing learning curves as the "right" solution.  I hate having to 
remember if links are [like this](url) or (this)[url] or even [url like 
this] (oh wait, that's the Trac style).  Google lets me do this 
 with a simple click.

To be productive on this front and not just complain, I did a fair amount 
of searching for wysiwyg or tinymce and jupyter and found almost nothing.  
Could this be a replacement?  https://github.com/bollwyvl/nb-wysiwyg  I 
also found this nice article 

 
which (correctly) claims "Why is Markdown better? Well, it’s worth saying 
that maybe it isn't. Mainly, it’s not actually a question of better or 
worse, but of what’s in front of you and of who you are. A definitive 
answer depends on the user and on that user’s goals and experience. These 
Notebooks don't use Markdown because it's definitely better, but rather 
because it's different and thus encourages users to think about their work 
differently."  But not everyone, especially those instructors in a hurry, 
have time to think about that on a first try.  If they end up writing a 
book I hope they do!  But if they just want to make an example for class 
it's a bit much.

Hopefully Jupyter will be able to have an option to have wysiwyg 
eventually, though I understand that might conflict with their design 
goals. In which case their design goals are not really for 
non-programmers.  

Practical example, lest someone think I'm beating up on a straw notebook 
interface:
Someone makes an awesome 3d plot in Jupyter with vectors and parametric 
things in red, blue, and green, labeling different things.  Now in the main 
body of their text they want the same output, so they can talk about green 
tangent vectors, blue normal vectors, and red curves, or something, in 
those colors.  Lovely stuff.  They Google how to do this in md and get:
http://stackoverflow.com/questions/19746350/how-does-one-change-color-in-markdown-cells-ipython-notebook
Result: the text stays all black for the presentation they have to do in 
ten minutes.

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread Daniel Krenn
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 hints that answer frequently asked questions:
>>
>> Type "%display unicode_art" for a nicer display of some outputs.
>> Type "implicit_multiplication(True)" for allowing implicit
>> multiplication.

-1 for crowding the banner with too many hints.

> "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 earlier.)

Best

Daniel

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread Jori Mäntysalo

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 earlier.)


help() with parameters to show longer help? (And smaller default than 
help() now prints.)


In an ideal world we would also have whatsnew() and maybe the system would 
see what version the user had used. But to make these we should see 
novices using Sage and get their comments. I have got no comments at all, 
not a single one, when I have written to math students here saying that 
now you have a direct connection to development of the software.


--
Jori Mäntysalo


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

2016-01-26 Thread Jori Mäntysalo

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 this
* I just make some comments on the ticket but would never set it to positive
review.


For last point see http://trac.sagemath.org/ticket/13250 and my comment "I 
have no other comments." There is nothing wrong about commenting a ticket, 
as long as it is clearly said to be only a comment, not a final rewiev. 
For docstrings it would be very good to have comments from those who do 
not read the code.


But long discussion about general principles in a specific ticket is bad.

Second point is what I wrote about. We should try to have a common view. 
OR explicit anti-rule to accept several styles. For example PEP-8 says 
"- - single-quoted strings and double-quoted strings are the same. This 
PEP does not make a recommendation - -"


--
Jori Mäntysalo


[sage-devel] Re: Matrix unicode output

2016-01-26 Thread Volker Braun
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 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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: Matrix unicode output

2016-01-26 Thread mmarco
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 domingo, 24 de enero de 2016, 18:10:27 (UTC+1), Nathann Cohen escribió:
>
> Hello everybody,
>
> I just noticed that M.str(unicode=True) (when M is a matrix) prints the 
> matrix very nicely (especially when it is a block matrix), with pretty 
> parentheses on both sides.
>
>   sage: print matrix.block(3,3,[matrix.ones(2)]*9).str(unicode=True)
>
> Would it be possible to make it the default behaviour? Through Volker's 
> machinery for auto-detection of output format, for instance?
>
> THaaanks,
>
> Nathann
>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: Matrix unicode output

2016-01-26 Thread Johan S . R . Nielsen
>
> 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 predefined
concepts. But of course, that's yet another entry-point documentation
that needs to be maintained...

Another possibility is that help() given a string could have a behaviour
similar to (the intention of) search_doc(). Right now, help() doesn't
mention the search_* functions, so you don't see those. So how would you
try to find information on typesetting?

Note that doing `search_doc("display")` gives completely unhelpful
output since it matches on the html-code (and therefore matches on the
CSS "display: none").

Best,
Johan

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] jsmol broken on JupyterHub

2016-01-26 Thread Christoph Ruegge
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 searching, and it seems as if the jsmol nbextension, in 
particular JSmol.min.js, is referenced via the path /nbextensions/jsmol 
from e.g. script tags, which is fine for Jupyter, but for JupyterHub 
probably needs to be prefixed with /user/$USER. Most requests under / 
apparently get redirected to /hub, where the JupyterHub API resides, but 
not the nbextensions. There is an option path_to_jsmol in the JSMolHtml 
class which might be used for this purpose, but it is apparently not 
properly set from backend_ipython.py.

I would be grateful for any advice.

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: jsmol broken on JupyterHub

2016-01-26 Thread Volker Braun
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) 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 searching, and it seems as if the jsmol nbextension, in 
> particular JSmol.min.js, is referenced via the path /nbextensions/jsmol 
> from e.g. script tags, which is fine for Jupyter, but for JupyterHub 
> probably needs to be prefixed with /user/$USER. Most requests under / 
> apparently get redirected to /hub, where the JupyterHub API resides, but 
> not the nbextensions. There is an option path_to_jsmol in the JSMolHtml 
> class which might be used for this purpose, but it is apparently not 
> properly set from backend_ipython.py.
>
> I would be grateful for any advice.
>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread jhonrubia6
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.show(ticks=pi/6, tick_formatter=pi)
I tried with
g._matplotlib_tick_formatter(subplot,ticks=(pi,None), tick_formatter=(pi,
None),xmax=10,xmin=0,ymax=10,ymin=0)
sphinx_plot(g)
but it does not render the pi symbol on the x axis
Any ideas on this?

(I move on meanwhile)



El jueves, 21 de enero de 2016, 20:45:31 (UTC+1), jhonrubia6 escribió:
>
> Does it makes sense to you if I modify the plot.py docstrings in order to 
> include PLOT:: blocks? Wouldn't it be more clear for newbies? (well it wold 
> have helped me anyway)
> Has it been discussed?
> Javier
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread Christian Stump
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 group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread Eric Gourgoulhon
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 receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread William Stein
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
before the actual parsing happens.  In this case the transformation
changes something that should be invalid syntax (if "the sage
language" had an official specified syntax, which it doesn't) into
something that is valid.  Amusing.

William

>
>
> --
> 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 sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.



-- 
William (http://wstein.org)

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


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

2016-01-26 Thread rjf
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 UTC-8, bluescarni wrote:
>
> It's somewhat refreshing to see that the idea that one should not use 
> black box software in science is finally starting to sink in.
>
> On 20 January 2016 at 13:30, William Stein  > wrote:
>
>> There's a big thread on Hacker News about math software in which Sage
>> is mentioned a few times:
>>
>> https://news.ycombinator.com/item?id=10934666
>>
>> I have the impression very few of the comments are from
>> mathematicians...  Nonetheless, some people may find the comments
>> interesting, since they reflect how open source math and scientific
>> software such as Sage/Python/Sympy/Octave are (mis-)perceived by one
>> group of potential users.
>>
>>  -- William
>>
>> --
>> 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 sage-devel+...@googlegroups.com .
>> To post to this group, send email to sage-...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: Getting Started

2016-01-26 Thread Samuel Lelievre
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 development process.

You can always get to the "Ticket reports" page by clicking the
"View tickets" button on the top left of the Sage trac home page

http://trac.sagemath.org/

Best, Samuel


Le mardi 26 janvier 2016 12:48:02 UTC, jhonrubia6 a écrit :
>
> 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 search trac to find a need_work ticket which appeals to you 
> as doable or open your own trac ticket on a bug if you happened to have 
> found one. If you think of an enhacement it is better to ask the community 
> on this forum for it may be implemented in some already written module.
> Hope it helps, and welcome.
>
> El martes, 19 de enero de 2016, 14:52:35 (UTC+1), Siddhartha Gairola 
> escribió:
>>
>> Dear Developers,
>>
>> I am a newbie and would like to get started.
>> I am in my sophomore year at college and i know c,c++,python,html,css and 
>> javascript.
>>
>> I would be highly grateful if i could get some assistance with this.
>>
>> Thanking you.
>>
>> Regards,
>> Siddhartha
>>
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: Getting Started

2016-01-26 Thread jhonrubia6
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 search trac to find a need_work ticket which appeals to you 
as doable or open your own trac ticket on a bug if you happened to have 
found one. If you think of an enhacement it is better to ask the community 
on this forum for it may be implemented in some already written module.
Hope it helps, and welcome.

El martes, 19 de enero de 2016, 14:52:35 (UTC+1), Siddhartha Gairola 
escribió:
>
> Dear Developers,
>
> I am a newbie and would like to get started.
> I am in my sophomore year at college and i know c,c++,python,html,css and 
> javascript.
>
> I would be highly grateful if i could get some assistance with this.
>
> Thanking you.
>
> Regards,
> Siddhartha
>

-- 
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.