On Mon, Jun 18, 2012 at 7:50 AM, Benjamin Root wrote:
> However, should it be a full-out error? Is it possible to have mpl run
> without a font cache?
I'm sure we could, but from an implementation perspective it would
probably be easier to spoof it with a virtual filesystem and files
using strin
On Mon, Jun 18, 2012 at 8:41 AM, John Hunter wrote:
> On Mon, Jun 18, 2012 at 7:29 AM, Martin Mokrejs
> wrote:
>
> > Hmm. Could it be by default the current working directory instead? Or,
> try/else added to the code
> > which would try to write into cwd if $HOME (aka $MPLCONFIGDIR) returns
> an
On Mon, Jun 18, 2012 at 7:29 AM, Martin Mokrejs
wrote:
> Hmm. Could it be by default the current working directory instead? Or,
> try/else added to the code
> which would try to write into cwd if $HOME (aka $MPLCONFIGDIR) returns an
> error?
The stuff we store there is meant to be persistent b
John Hunter wrote:
>
>
>
>
> On Jun 18, 2012, at 6:19 AM, Martin Mokrejs
> wrote:
>
>> Hi,
>> I am running some script in /mnt/blah and while my $HOME disk on a
>> different device filled up
>> because of some other reason. But my script ran in /mnt/blah died as well
>> while there is p
On Jun 18, 2012, at 6:19 AM, Martin Mokrejs wrote:
> Hi,
> I am running some script in /mnt/blah and while my $HOME disk on a different
> device filled up
> because of some other reason. But my script ran in /mnt/blah died as well
> while there is plenty
> of space. Here is the stacktrace.
Hi,
I am running some script in /mnt/blah and while my $HOME disk on a different
device filled up
because of some other reason. But my script ran in /mnt/blah died as well while
there is plenty
of space. Here is the stacktrace.
import matplotlib
File "/usr/lib64/python2.7/site-packages/m
