No, there isn't an accepted way to do that AFAIK. However, it doesn't seem like it is all that far off. Our doc-build process will create the images from the examples automatically, so you don't need to include the image tag. It is sort of a way to make sure the examples work and that the image matches the code correctly.
On Mon, Jun 8, 2015 at 1:06 PM, Jody Klymak <jkly...@uvic.ca> wrote: > > Hi all, > > If I want to contribute *.rst files to the matplotlib documentation, I can > see a few styles already contributed, at least one of which makes extensive > use of ipython (http://matplotlib.org/users/image_tutorial.html). > However, even it makes use of `.. sourcecode:: python` and `.. plot::` > blocks. > > If I convert an ipython notebook to rst, it formats as: `.. code:: python` > and instead of making plots it loads images: > `.. image:: MyExample_files/MyExample_1_0.png` > > So, is there an acceptable way to directly make matplotlib documentation > directly from a notebook? I didn’t see anything, but wanted to check, as > that would by far be the easiest way to make a *.rst that had structured > text, code, and plots. > > Thanks, Jody > > -- > Jody Klymak > http://web.uvic.ca/~jklymak/ > > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
------------------------------------------------------------------------------
_______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
