From: Fernando P. <Fer...@co...> - 2005-06-22 22:35:41
|
Stephen Walton wrote: > Fernando Perez wrote: > > >>Well, it could be something like $HOME/.tex.cache, where $HOME can be >>determined via a routine like the below (this is what ipython uses to >>try and guess a sensible value for $HOME): > > > I *like* it. Though I'd personally vote for matplotlib holding $HOME/.matplotlib/ as a directory, and putting in there a tex.cache dir, the matplotlibrc file, and anything else it may need in the future. I *really* don't like the idea that matplotlib will begin to put a bunch of differently named things under $HOME with various .foo names. Ipython also started with .ipythonrc, and I quickly moved to an .ipython/ directory, where I stuff anything I need. It's future-proof, clean, and gives an easy way for users to clean up if needed, without having to guess 'how many dot files/directories does this thing create'? So if you were to ask for my opinion, I'd vote +100 on matplotlib moving to a single directory for holding *ALL* user and configuration data, which would default to $HOME/.matplotlib, and which could be overridden if the $MATPLOTLIBDIR environment variable is defined. That's exactly how ipython works, so it must be the perfect solution :) Cheers, f |