Open GoogleCodeExporter opened 9 years ago
I think the source images are not included in the release tar.gz, but they are
available in an svn checkout. If you are making a package for Fedora, you may
want to
add them.
Original comment by fredrik....@gmail.com
on 19 Oct 2009 at 2:04
That's good. This means both images don't need to be generated in the build,
they are
missing in the tar.gz.
So no problem why building :)
Original comment by thomas.s...@gmail.com
on 19 Oct 2009 at 5:45
Could you add them in the next release?
Original comment by thomas.s...@gmail.com
on 19 Oct 2009 at 5:49
There is a problem with that; they would significantly increase the file size.
Perhaps I can make them smaller.
Original comment by fredrik....@gmail.com
on 19 Oct 2009 at 5:55
What about a seperate tar ball for the images?
Original comment by Vinzent.Steinberg@gmail.com
on 29 Oct 2009 at 7:46
Good idea. Would also make it easier to add more graphical examples to the docs.
Original comment by fredrik....@gmail.com
on 30 Oct 2009 at 2:48
I added them for now; 80 KB extra is not the end of the world in this day and
age.
But we should definitely figure out a way to generate graphics from plot
commands in
the docstrings when building the docs.
Original comment by fredrik....@gmail.com
on 4 Feb 2010 at 1:52
Agreed.
Original comment by Vinzent.Steinberg@gmail.com
on 4 Feb 2010 at 12:18
This should be possible to do using the Sphinx matplotlib extension:
http://matplotlib.sourceforge.net/sampledoc/extensions.html
Original comment by fredrik....@gmail.com
on 5 Feb 2010 at 9:33
I've added a bunch of images in r1153.
Starting with the next version, the documentation will probably be released
separately since the images take up quite a lot of space (and more to be added).
It would be possible not to include the images in the doc sources, and just
generate them with the documentation build script. Unfortunately, it takes
quite a lot of time to generate all the plots from scratch (especially the
complex color plots), so I don't know about that.
Alas, I've had no luck with the Sphinx matplotlib extension, so the current
solution for including plots is a bit of a hack :)
Original comment by fredrik....@gmail.com
on 14 Jun 2010 at 7:30
So we should probably get in touch with upstream.
Original comment by Vinzent.Steinberg@gmail.com
on 14 Jun 2010 at 9:07
It's a matplotlib issue (it crashes for me when attempting to import the
utility modules).
I tried asking on the matplotlib mailing list a while back, but there wasn't
sufficient information to figure out the cause of the crash.
Original comment by fredrik....@gmail.com
on 14 Jun 2010 at 9:10
Original issue reported on code.google.com by
thomas.s...@gmail.com
on 19 Oct 2009 at 1:06