[Numpy-discussion] c-info.ufunc-tutorial.rst

2011-08-24 Thread srean
Hi, I was reading this document, https://github.com/numpy/numpy/blob/master/doc/source/user/c-info.ufunc-tutorial.rst its well written and there is a good build up to exciting code examples that are coming, but I do not see the actual examples, only how they may be used. Is it located somewhere

Re: [Numpy-discussion] c-info.ufunc-tutorial.rst

2011-08-24 Thread srean
Following up on my own question: I can see the code in the commit. So it appears that code-block:: Are not being rendered correctly. Could anyone confirm ? In case it is my browser alone, though I did try after disabling no-script. On Wed, Aug 24, 2011 at 6:53 PM, srean srean.l...@gmail.com

Re: [Numpy-discussion] c-info.ufunc-tutorial.rst

2011-08-24 Thread Mark Wiebe
On Wed, Aug 24, 2011 at 5:05 PM, srean srean.l...@gmail.com wrote: Following up on my own question: I can see the code in the commit. So it appears that code-block:: Are not being rendered correctly. Could anyone confirm ? In case it is my browser alone, though I did try after disabling

Re: [Numpy-discussion] c-info.ufunc-tutorial.rst

2011-08-24 Thread Anthony Scopatz
code-block:: is a directive that I think might be specific to sphinx. Naturally, github's renderer will drop it. On Wed, Aug 24, 2011 at 7:10 PM, Mark Wiebe mwwi...@gmail.com wrote: On Wed, Aug 24, 2011 at 5:05 PM, srean srean.l...@gmail.com wrote: Following up on my own question: I can see

Re: [Numpy-discussion] c-info.ufunc-tutorial.rst

2011-08-24 Thread srean
Thanks Anthony and Mark, this is good to know. So what would be the advised way of looking at freshly baked documentation ? Just look at the raw files ? or is there some place else where the correct sphinx rendered docs are hosted. On Wed, Aug 24, 2011 at 7:19 PM, Anthony Scopatz

Re: [Numpy-discussion] c-info.ufunc-tutorial.rst

2011-08-24 Thread josef . pktd
On Wed, Aug 24, 2011 at 8:43 PM, Anthony Scopatz scop...@gmail.com wrote: On Wed, Aug 24, 2011 at 7:34 PM, srean srean.l...@gmail.com wrote: Thanks Anthony and Mark, this is good to know. So what would be the advised way of looking at freshly baked documentation ? Just look at the raw