On Mon, Jul 19, 2010 at 5:22 PM, Eric Firing <efir...@hawaii.edu> wrote: > 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.
The primary motivation for the get_sample_data code arose from my observation that the gallery had become extremely popular, and appeared to be the way most people learned/experimented with mpl. I wanted some way to make it easy for a user to download and run any example from the gallery. One could say, "grab this tarball or zipfile and unpack it before running this example", but getting the relative paths right, especially on windows, is difficult for new users. I completely agree that we can and should support a mechanism for users / distributors who want to circumvent the download phase. One could have an rc param "sampledata.localonly" that would check the mpl config dir for a sample_data dir (which is where it looks already) and forgo all the revision control stuff: if the file is there load it, else raise. Or we could support a special MPLSAMPLEDATA env var which could point to a dir or even a tar/zip file. Then one could get a svn co of sample_data, zip it up when going out to sea or packaging mpl, and configure mpl, presumably via the rc mechanism or env vars to use the hardcopy. JDH ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
