Darren Dale wrote:
> On Monday 30 April 2007 02:31:59 pm Eric Firing wrote:
>> One way this could happen is if the .matplotlib directory exists but is
>> not writable; such a case would give the error traceback you see with
>> little clue as to what and where the problem really is. So, __init__.py
Hi Eric,
Thanks for your response.
> One way this could happen is if the .matplotlib directory exists
> but is not writable; such a case would give the error traceback you
> see with little clue as to what and where the problem really is.
> So, __init__.py certainly could be improved.
On Monday 30 April 2007 02:31:59 pm Eric Firing wrote:
> One way this could happen is if the .matplotlib directory exists but is
> not writable; such a case would give the error traceback you see with
> little clue as to what and where the problem really is. So, __init__.py
> certainly could be im
One way this could happen is if the .matplotlib directory exists but is
not writable; such a case would give the error traceback you see with
little clue as to what and where the problem really is. So, __init__.py
certainly could be improved. (Offhand, I don't even know why the
existence of s
Hi all,
I recently run into a problem with the .matplotlib directory. I run a
script as a daemon, that in its turn runs several scripts to create
graphs (often the same script with different input parameters),
dependent on an outside trigger. Recently, I found that these script
crashed
