First, you folks respond faster than lightning -- I can't keep up!
Second, thanks for the tip -- that's definitely more elegant than my callow
approach.
John Hunter-4 wrote:
>
> On Thu, Sep 1, 2011 at 1:23 PM, CompBio wrote:
>
>> BTW, the reason I specify a PDF backend is because I thought i
On Thu, Sep 1, 2011 at 1:23 PM, CompBio wrote:
> BTW, the reason I specify a PDF backend is because I thought it would tell
> matplotlib not to try to use anything else "behind the scenes" such as an
> X-window display. It's working the way I want now, so I assume that's what
> it's doing.
But
Thanks for your fast response -- faster than I could post a follow-up.
You're right about the stack trace. It occurred to me after I posted that I
should look to see exactly where the exception was triggered. As it turned
out, I'd added a new module a few days ago and wasn't careful about where
On 09/01/2011 05:37 AM, CompBio wrote:
>
> I'm trying to get a script to work in batch mode to produce a large number of
> plots. I've got the following sequence of imports in a matplotlib Python
> script:
Is the script being run standalone, from a shell, and are the following
the very first imp
On Thursday, September 1, 2011, CompBio wrote:
>
> I'm trying to get a script to work in batch mode to produce a large number
of
> plots. I've got the following sequence of imports in a matplotlib Python
> script:
>
> import matplotlib, os, sys
> ...
> if file_ext == 'png' :
>sys.stderr.write
I'm trying to get a script to work in batch mode to produce a large number of
plots. I've got the following sequence of imports in a matplotlib Python
script:
import matplotlib, os, sys
...
if file_ext == 'png' :
sys.stderr.write('Using PNG output format\n')
matplotlib.use('agg')
elif fi
