On Sun, Jun 26, 2011 at 9:05 PM, Benjamin Root <ben.root@...> wrote:
> On Sunday, June 26, 2011, Warren Weckesser
> <warren.weckesser@...> wrote:
> > On Sun, Jun 26, 2011 at 7:44 PM, Benjamin Root <ben.root@...> wrote:
> > On Sunday, June 26, 2011, Carl Karsten <carl@...> wrote:
> >> http://matplotlib.sourceforge.net/examples/api/radar_chart.html
> >> "Exception occurred rendering plot."
> > Without more information, we can't help you. What version of
> > matplotlib are you using? On what OS? How did you install it? Do the
> > tests pass? And which backend?
> > That error is what shows up on the web page when you follow the link.
> > Warren
> Ah, indeed it is. I apologize for misunderstanding, what is odd is
> that the demo didn't work, but the mpl logo rendered fine.
> Who was it that uploaded the recent rebuild of the docs?
> Ben Root
I just had an epiphany and figured out what is causing this. It looks like
that any example that uses the "if __name__ == '__main__' :" idiom is
failing to produce an image. Some others that have the same issue are:
http://matplotlib.sourceforge.net/examples/api/sankey_demo.htmlhttp://matplotlib.sourceforge.net/examples/api/hinton_demo.htmlhttp://matplotlib.sourceforge.net/examples/api/logo2.html (it has a link,
but no image on the page)
and many others (can be found by grepping for "__main__" in the examples
On a local build of the docs from master, axes_grid has two demos that also
fail to produce images for the docs. They look to be new demos.
I wonder if this is being caused (or at least the errors hidden by) the new
multiprocessing approach for the doc-build. Anybody have any thoughts on
how to deal with this? I consider this a release-stopper.