matplotlib-devel Mailing List for matplotlib

> > So now on the 1.0 maintenance branch (coming soon to trunk, once I'm
> > done wrangling with svnmerge) you can set new rc parameters
> > examples.download to False and examples.directory to the directory
> > 
> How would one set these during the build process? Is there a way to pass
> in rc parameters via environment variable? Perhaps we should just patch
> matplotlibrc.template in the tree? Any ideas would be appreciated,

I can't check right now how the doc build works, but I think you could either patch the build script to set the parameters programmatically or drop a matplotlibrc file in the relevant directory.

Jouni

On Sun, 07 Nov 2010 10:25:13 +0200, Jouni K. Seppänen <jk...@ik...> wrote:
> So now on the 1.0 maintenance branch (coming soon to trunk, once I'm
> done wrangling with svnmerge) you can set new rc parameters
> examples.download to False and examples.directory to the directory where
> you have a checkout of the sample data¹. Then get_sample_data will only
> look in this directory and not download anything.
> 
How would one set these during the build process? Is there a way to pass
in rc parameters via environment variable? Perhaps we should just patch
matplotlibrc.template in the tree? Any ideas would be appreciated,

- Ben

On Sun, Nov 7, 2010 at 3:25 AM, Jouni K. Seppänen <jk...@ik...> wrote:
> So now on the 1.0 maintenance branch (coming soon to trunk, once I'm
> done wrangling with svnmerge) you can set new rc parameters
> examples.download to False and examples.directory to the directory where
> you have a checkout of the sample data¹. Then get_sample_data will only
> look in this directory and not download anything.
>
> Does this help with the Debian and Ubuntu builds?
>

I believe that should help. Hopefully someone on the bug with more
knowledge of the policy will comment to confirm.

- Ben

Jouni K. Seppänen <jk...@ik...> writes:

> Benjamin Root <ben...@ou...> writes:
>
>>> As an Ubuntu user, I would really a mechanism
>>> for excluding examples requiring downloaded data from being built 
>>
>> How far did we get on that?  I could have sworn  we did something
>> about the caching mechanism.  
>
> I'll commit something simple to deal with this, since the fancier
> plans were apparently too much.

So now on the 1.0 maintenance branch (coming soon to trunk, once I'm
done wrangling with svnmerge) you can set new rc parameters
examples.download to False and examples.directory to the directory where
you have a checkout of the sample data¹. Then get_sample_data will only
look in this directory and not download anything.

Does this help with the Debian and Ubuntu builds?

¹ https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/trunk/sample_data

-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Benjamin Root <ben...@ou...> writes:

>> As an Ubuntu user, I would really a mechanism
>> for excluding examples requiring downloaded data from being built 
>
> How far did we get on that?  I could have sworn  we did something
> about the caching mechanism.  

I think there were some discussions (something to do with the transition
to git, and putting test results in the same mechanism), but at least I
never got around to writing any code, and then got distracted by my day
job. I'll commit something simple to deal with this, since the fancier
plans were apparently too much.

-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On Saturday, November 6, 2010, Ben Gamari <bga...@gm...> wrote:
> Hey all,
>
> Not so long ago there was a brief discussion concerning the release
> schedule for 1.0.1[1]. As an Ubuntu user, I would really a mechanism
> for excluding examples requiring downloaded data from being built for
> the doc target. This would bring matplotlib into compliance with
> Debian packaging policy[3].
>
> Cheers,
>
> - Ben
>
>
> [1] http://sourceforge.net/mailarchive/forum.php?thread_name=01aa01cb76eb$0d1d7ea0$27587be0$%40net&forum_name=matplotlib-devel
> [2] https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/607395
> [3] http://thread.gmane.org/gmane.comp.python.matplotlib.devel/8865
>
> ------------------------------------------------------------------------------
> The Next 800 Companies to Lead America's Growth: New Video Whitepaper
> David G. Thomson, author of the best-selling book "Blueprint to a
> Billion" shares his insights and actions to help propel your
> business during the next growth cycle. Listen Now!
> http://p.sf.net/sfu/SAP-dev2dev
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

How far did we get on that?  I could have sworn  we did something
about the caching mechanism.  What exactly still remains to be done to
be in compliance?  Lastly, I am not 100% familiar with the doc build
system, but does't simply check to see if there are newer code?
Couldn't that simply be disabled?

Ben Root

Hey all,

Not so long ago there was a brief discussion concerning the release
schedule for 1.0.1[1]. As an Ubuntu user, I would really a mechanism
for excluding examples requiring downloaded data from being built for
the doc target. This would bring matplotlib into compliance with
Debian packaging policy[3].

Cheers,

- Ben


[1] http://sourceforge.net/mailarchive/forum.php?thread_name=01aa01cb76eb$0d1d7ea0$27587be0$%40net&forum_name=matplotlib-devel
[2] https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/607395
[3] http://thread.gmane.org/gmane.comp.python.matplotlib.devel/8865