#6235: set MPLCONFIGDIR environment variable when Sage starts up
----------------------+-----------------------------------------------------
Reporter: was | Owner: cwitty
Type: defect | Status: new
Priority: minor | Milestone: sage-4.6
Component: misc | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------+-----------------------------------------------------
Comment(by jason):
Replying to [comment:11 leif]:
> Replying to [comment:10 jhpalmieri]:
> > Can we just do
> {{{
> MPLCONFIGDIR="$DOT_SAGE/matplotlib"
> export MPLCONFIGDIR
> }}}
> > in sage-env?
>
> As mentioned above, the configuration should be inside a ''specific Sage
installation'' hierarchy, not just yet another ''user-specific''
directory, which is (usually) the same for all Sage installations.
At the same time, this directory should not be inside a specific Sage
installation (i.e., below SAGE_ROOT) since that means system-wide installs
can't have individual customizations, and it also breaks system-wide font
cache generation (i.e., matplotlib assumes that a user can update the font
cache file, I believe). So where are we now? Separate matplotlib config
directories for each version of Sage inside of the .sage directory?
>
> I don't understand why the matplotlib developers broke compatibility
with older versions; I think it's likely to have different MPL
installations included in other software packages, but I might be wrong.
IMHO bad design anyway; also the exceptions raised are odd.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6235#comment:12>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
