matplotlib-users Mailing List for matplotlib

>>>>> "Chris" == Chris Barker <Chr...@no...> writes:
 Chris> Do you mean me? If so, I'm not sure, what I've objected to
 Chris> a lot are two things: procedural, rather than OO style; and
 Chris> compatibility with Matlab, rather than Python. Magic is OK,
 Chris> as long as it's easily over-written. In this case, as long
 Chris> as I can do:
OK, my bad. I was confusing your criticism of the procedural style of
the pylab interface with others criticism of the magic. Both are
valid, and both need to be able to be "turned off' which the OO
interface does...
 Chris> I'm not the OP, but I got the impression that his
 Chris> .matplotlibrc had numarray in it, even though it was not
 Chris> installed, and he hadn't edited it, so there was a mistake
 Chris> somewhere. Where, I don't know.
I don't think that's likely, unless was using an STScI matplotlib OS X
distribution, which I think they ship, or did ship at one point.
JDH

Hej Andrew,
intersting solution! just a couple of days ago I was struggeling with
the same problem
I solved it by setting the environment variable from within my CGI script
the following is a template for a cgi that uses matplotlib to create a
png figure:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#!/usr/bin/python
import cgitb; cgitb.enable()
# set HOME environment variable to a directory the httpd server can write t=
o
import os
myenv =3D os.environ
myenv['HOME'] =3D '/tmp/'
# chose a non-GUI backend
import matplotlib
matplotlib.use('Agg')
# construct your plot
from pylab import *
...
# save the plot as image
savefig(...)
On 11/5/05, Andrew P <gr...@gm...> wrote:
> OK, scratch that. Typing it out helped me see where my assumptions
> were screwy. You can set environment variables quite happily in
> .htaccess.
>
> If this gets past moderation, you can just do this:
>
> SetEnv HOME /user/home/directory
>
> In .htaccess and it fixes it right up :)
>
> On 11/4/05, Andrew P <gr...@gm...> wrote:
> > Hello all,
> >
> > Matplotlib raises this error when I import it as a CGI program:
> >
> > RuntimeError: '/var/www' is not a writable dir; you must set
> > environment variable HOME to be a writable dir
> >
> > I am a non-root user, and the Apache user's HOME =3D/var/www, so CGI
> > script raises an exception when that directory isn't writeable. There
> > is nothing to be done about the Apache users's environment variables,
> > or the writablity of that directory, as a non-root user :)
> >
> > It appears that matplotlib checks the HOME environment variable, then
> > the MATPLOTLIBDATA variable, and then goes on to check the
> > matplotlibrc starting with the current directory. But it raises an
> > exception if the home directory isn't writeable without checking the
> > rc file to see if the datapath inside it would work?
> >
> > Is there a way to either prevent matplotilb from checking for HOME,
> > and go straight to the local matplotlibrc, or alternately have it
> > check the matplotlibrc if the HOME directory isn't writable?
> >
> >
> > Thanks,
> >
> > Andrew
> >
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Downl=
oad
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On 11/4/05, Chris Barker <Chr...@no...> wrote:
>
> Paul Barrett wrote:
> >>How about a setup.py option where you can explicitly set numeric or
> >
> > numarray, such as "--use=3Dnumarray"? This optional will build MPL for
> > numarray and modify the rc file so that it doesn't have to be edited by
> > hand.
>
> I'm confused. Is this a proposal, or is it implemented now? Either way,
> I like it.
>
It's a proposal. It's also explicit. :-)
-- Paul

Hello all,
Matplotlib raises this error when I import it as a CGI program:
RuntimeError: '/var/www' is not a writable dir; you must set
environment variable HOME to be a writable dir
I am a non-root user, and the Apache user's HOME =3D/var/www, so CGI
script raises an exception when that directory isn't writeable. There
is nothing to be done about the Apache users's environment variables,
or the writablity of that directory, as a non-root user :)
It appears that matplotlib checks the HOME environment variable, then
the MATPLOTLIBDATA variable, and then goes on to check the
matplotlibrc starting with the current directory. But it raises an
exception if the home directory isn't writeable without checking the
rc file to see if the datapath inside it would work?
Is there a way to either prevent matplotilb from checking for HOME,
and go straight to the local matplotlibrc, or alternately have it
check the matplotlibrc if the HOME directory isn't writable?
Thanks,
Andrew

John Hunter wrote:
> This is what I do for the win32 builds -- hand edit the file before
> each build. A little bit of a pain, bit it works (as long as you
> remember to tweak the file before the build <wink>)
I guess I could write a little script that did it for me easily enough. 
Who else is building MPL on OS-X. I may not have as much need for it 
now, we're moving a web app that uses it from an OS-X box to a Linux box.
> I think we would readily accept a patch for either or both of these,
> but there are those who already despise the amount of magic that pylab
> engages in (and you are usually near the front of that chorus).
Do you mean me? If so, I'm not sure, what I've objected to a lot are two 
things: procedural, rather than OO style; and compatibility with Matlab, 
rather than Python. Magic is OK, as long as it's easily over-written. In 
this case, as long as I can do:
import matplotlib
matplotlib.use(...)
I'm happy.
> Yes,
> explicit is (usually) better than implicit, but this tends to conflict
> with "just works".... Are you starting to experience a change of
> heart :-) ?
I like to think I've been totally consistent....
> In your use case is this correct, or do we need to amend the build,
> runtime or docs? According to your post, we should fall back on
> Numeric if numarray is specified but not present. Reasonable, but
> also a bit counter-intuitive since Numeric is the default and in this
> case the user would have explicitly overridden the default.
I'm not the OP, but I got the impression that his .matplotlibrc had 
numarray in it, even though it was not installed, and he hadn't edited 
it, so there was a mistake somewhere. Where, I don't know.
-CHB
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

OK, scratch that. Typing it out helped me see where my assumptions
were screwy. You can set environment variables quite happily in
.htaccess.
If this gets past moderation, you can just do this:
SetEnv HOME /user/home/directory
In .htaccess and it fixes it right up :)
On 11/4/05, Andrew P <gr...@gm...> wrote:
> Hello all,
>
> Matplotlib raises this error when I import it as a CGI program:
>
> RuntimeError: '/var/www' is not a writable dir; you must set
> environment variable HOME to be a writable dir
>
> I am a non-root user, and the Apache user's HOME =3D/var/www, so CGI
> script raises an exception when that directory isn't writeable. There
> is nothing to be done about the Apache users's environment variables,
> or the writablity of that directory, as a non-root user :)
>
> It appears that matplotlib checks the HOME environment variable, then
> the MATPLOTLIBDATA variable, and then goes on to check the
> matplotlibrc starting with the current directory. But it raises an
> exception if the home directory isn't writeable without checking the
> rc file to see if the datapath inside it would work?
>
> Is there a way to either prevent matplotilb from checking for HOME,
> and go straight to the local matplotlibrc, or alternately have it
> check the matplotlibrc if the HOME directory isn't writable?
>
>
> Thanks,
>
> Andrew
>

Paul Barrett wrote:
>>How about a setup.py option where you can explicitly set numeric or
> 
> numarray, such as "--use=numarray"? This optional will build MPL for
> numarray and modify the rc file so that it doesn't have to be edited by
> hand.
I'm confused. Is this a proposal, or is it implemented now? Either way, 
I like it.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...