On 07/19/2010 11:10 AM, Sandro Tosi wrote:
> you know this question might seems strange, but I'd like to avoid some
> examples to be built when creating documentation.
> Those examples are the one using mpl.cbook.get_sample_data() to
> retrieve data files from the remote svn. In Debian we are not allowed
> to prepare a package that downloads "stuff" from the web, so I have to
> avoid this.
> The fastest solution I see is to actually exclude them from the list
> of the examples to build (but still install them, for users to use),
> but I didn't understand how :)
> Another solution would be for you to ship those datafile into the
> released tarball, so that it's all consistent and then point the
> example to those files, but how? if you find this in some way
> unacceptable, I can also download those files separately and add them
> when preparing the Debian package, but I have to find a way to tell
> get_sample_data() to point to that location...
> ...and so I'm asking you: what would you feel to be the best solution?
I think we should include any necessary data, and also eliminate the
downloading from the examples run by the standard backend_driver. The
caching doesn't seem to work right, and there are long timeouts. This
was a problem for me recently when I was out on a ship, working on mpl
on a computer without a live internet connection.
It would be OK to retain some examples with live downloading, but they
should not be required for doc generation or for basic testing of mpl.
They don't contribute anything essential to either.
> Thanks in advance for your help and suggestions,