If you don't have any special use for the config dir, this might be a
more straightforward solution that doesn't require patching matplotlib.
Simply paste this in your code, before importing matplotlib :
import os
os.environ['HOME'] = '/tmp/'
Might be safer to use 'MPLCONFIGDIR' instead of
On Thu, Nov 4, 2010 at 10:49 AM, Philip Semanchuk phi...@semanchuk.com wrote:
Hi all,
I've run into an aspect of matplotlib's setup that seems awkward. I'm seeing
this on Ubuntu, but I imagine it would happen on any *nix platform.
If python is running under sudo the first time matplotlib is
On Mon, Nov 8, 2010 at 8:34 AM, Philip Semanchuk phi...@semanchuk.com wrote:
Hi Ryan,
Thanks. I don't know why sudo behaves the way it does with regard to $HOME,
but the behavior of sudo is not under my control (nor matplotlib's). Also, I
expect that *lots* of software depends on this
On Nov 8, 2010, at 9:51 AM, Ryan May wrote:
On Mon, Nov 8, 2010 at 8:34 AM, Philip Semanchuk phi...@semanchuk.com wrote:
Hi Ryan,
Thanks. I don't know why sudo behaves the way it does with regard to $HOME,
but the behavior of sudo is not under my control (nor matplotlib's). Also, I
expect
Hi all,
I've run into an aspect of matplotlib's setup that seems awkward. I'm seeing
this on Ubuntu, but I imagine it would happen on any *nix platform.
If python is running under sudo the first time matplotlib is imported, then
matplotlib creates its config dir (~/.matplotlib) with root as the
