Jouni K. Seppänen wrote:
> No, that's exactly what I was thinking about - some newly-found font
> might break matplotlib, or might change somebody's output because of the
> font matching algorithm.
> Actually, the font matching system can
> sometimes break things:
>
> http://thread.gmane.org/gmane
No, that's exactly what I was thinking about - some newly-found font
might break matplotlib, or might change somebody's output because of the
font matching algorithm. Actually, the font matching system can
sometimes break things:
http://thread.gmane.org/gmane.comp.python.matplotlib.general/18255/f
Sorry about that bug. Obviously it wasn't tested properly.
It seems like the only side effect of this change is that matplotlib
will pull in fonts from non-standard locations defined in their
fontconfig configuration. (It's already pulling them from standard
locations that are hardcoded in fo
Because of the problem described here:
http://thread.gmane.org/gmane.comp.python.matplotlib.general/20328
I modified font_manager.py to use subprocess.Popen instead of
commands.getstatusoutput, since subprocess seems to deal with EINTR
while the commands module does not. While looking at it, I ch
