Re: [matplotlib-devel] How to exclude some examples to be built for doc?
Hello, On Mon, Jul 19, 2010 at 23:10, Sandro Tosi mo...@debian.org wrote: Hello, 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 don't want to put pressure on this but... was there any progress? :) It would be nice to have this somehow fixed or worked-around, so that I can upload to debian (experimental branch) and get some testing there. The fact doc generation requires downloading datafiles from web it's the only thing left that holds upload of mpl. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] How to exclude some examples to be built for doc?
Hello, 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? Thanks in advance for your help and suggestions, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- 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
Re: [matplotlib-devel] How to exclude some examples to be built for doc?
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
