On Wed, Aug 24, 2011 at 8:43 PM, Anthony Scopatz <[email protected]> wrote: > > > On Wed, Aug 24, 2011 at 7:34 PM, srean <[email protected]> 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 files ? or is there some place else where the correct >> sphinx rendered docs are hosted. > > Building the docs yourself is probably the safest bet. However, someone > should probably hook up the numpy and scipy repos to readthedocs.org. That > would solve this problem...
Maybe someone just needs to add it here http://docs.scipy.org/numpy/docs/numpy-docs/user/c-info.rst/#c-info and it would show up in numpy's own docs, which are hooked up to the repo, as far as I know. Josef > >> >> On Wed, Aug 24, 2011 at 7:19 PM, Anthony Scopatz <[email protected]> >> wrote: >>> >>> 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 <[email protected]> wrote: >>>> >>>> I believe this is because of github's .rst processor which simply drops >>>> blocks it can't understand. When building NumPy documentation, many more >>>> extensions and context exists. I'm getting the same thing in the C-API >>>> NA-mask documentation I just posted. >>>> -Mark >> >> _______________________________________________ >> NumPy-Discussion mailing list >> [email protected] >> http://mail.scipy.org/mailman/listinfo/numpy-discussion >> > > > _______________________________________________ > NumPy-Discussion mailing list > [email protected] > http://mail.scipy.org/mailman/listinfo/numpy-discussion > > _______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
