matplotlib-users Mailing List for matplotlib

Michael:

I commented on the patch here:

https://github.com/matplotlib/matplotlib/issues/545

In short...it works!

2011/10/21 Friedrich Romstedt <fri...@gm...>:
> I will try to dig out that emails.

Did that, the email I meant dates back to 10 November 2010!  Here's the snippet:

<snippet>

(Ben Root):
> I am curious, could this approach you have done be generalized to any sort
> of color transformation?  Admittedly, a gray mode is probably the most
> common request, but what if someone wants a different transformation?  Maybe
> even apply a filter that would produce sepia colors, or high-contrast
> colors, or a different grayscale transform?  Heck, I could imagine a use
> where a user might want to do a color substitution?

Oh Yes, this is *ealily* possible.  The new framework in the
ColorConverter class just uses a filter function, if we want to see it
like that, already.  It's just the apply_rc_gray_setting() function or
sth like that.  If you want to, you can try to add the functionality.
But we should discuss beforehand how to design it.  There are several
possibilites.  In fact, I like this filter function quite a lot!

1)  Hardcoding other filters in ColorConverter (what a decent name!),
and switching them on or off
2)  Inserting filters as functions on runtime into the ColorConverter
instance, some hooking mechanism
3)  Providing a dedicated Filter class, that can be fed to
set_filter() instead of set_gray().  This I like best.

I will, when i find some time, first implement the propagation of gray
settings by allowing objects in set_gray().  Might be a good time to
rename it to set_filter() right away, or maybe not do it, if
set_gray() goes in, and expects a bool, it might break compat when
changing the argument spec later.  So later set_gray() would just call
set_filter() or add_filter() or whatever.

</snippet>

So the filter idea was Ben's idea.  I still like idea (3) for the
design best.  I will check if it is possible to inject the filter code
into the renderer framework, since all colour settings arguments
somewhen flow into a call into the renderer.  Pro: No rcParams
addition necessary, no modification of the peculiar colors.py
ColorConverter framework necessary, just leaving those things
untouched and hence no worries and headaches about them.  No disabling
of higher-level caching and at the same time negligible small impact
if there is no filter active.  Con: I don't know yet if it works.  I
vaguely remember there were some problems when I checked that
possibility last time (with pixmaps or something like that).  I think
I will find out soon enough.

Eric, Ben, do you think we should go off-list with this now?  I would
prefer on-list now.  There might be people following but not
responding.

Friedrich

On 10/22/2011 06:46 AM, Steve Butcher wrote:
> All,
>
> On my iMac at work running 10.6.8, I did a brew-based installation of
> Python 2.7.2. I used pip to install scipy, numpy and then matplotlib.
> The last didn't work right so I scoured the internets to find out what
> to do. The first solution I found suggested doing a git clone of the
> repository and running python setup.py build then python setup.py
> install. That worked just great.
>
> At home, I tried the same thing on my MBP running 10.6.8. When I got to
> the compile matplotlib step, the fix from above didn't work. So I
> started trying other solutions I had found. Many of them "worked",
> however, when I went to run this simple script:
>
> import matplotlib.pylab as plt
> from scipy.stats import norm
>
> I got this error:
>
> Traceback (most recent call last):
> File "plot.py", line 1, in <module>
> import matplotlib.pylab as plt
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/pylab.py",
> line 221, in <module>
> from matplotlib import mpl # pulls in most modules
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/mpl.py",
> line 2, in <module>
> from matplotlib import axis
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/axis.py",
> line 10, in <module>
> import matplotlib.font_manager as font_manager
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py",
> line 1323, in <module>
> _rebuild()
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py",
> line 1273, in _rebuild
> fontManager = FontManager()
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py",
> line 997, in __init__
> self.afmlist = createFontList(self.afmfiles, fontext='afm')
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py",
> line 565, in createFontList
> prop = afmFontProperty(fpath, font)
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py",
> line 501, in afmFontProperty
> weight = weight_as_number(font.get_weight().lower())
> File
> "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/afm.py",
> line 464, in get_weight
> return self._header['Weight']
> KeyError: 'Weight'
>
> Googling did not reveal a single occurrence of this error reported anywhere.
>
> And so I would move on to the next instructions for compilation
> including the original make.osx instructions...and while the
> compilations succeeded, I still got the same error. Finally I decided to
> try the Enthought completely pre-compiled and packaged installation.
> Same problem.
>
> I'm at a loss. I even completely erased my /usr/local/ directory so that
> everything would be consistently installed via Homebrew. But no matter
> what I do, I end up with the same problem.
>
> I'm considering that something is wrong with my Snow Leopard
> installation and perhaps (reluctantly) upgrading to Lion, something I
> haven't really felt compelled to do. I'm hoping that there is a setting
> that I neglected.
>
> Ideas?

Given that the error is appearing in afm.py, and that it is independent 
of the python and matplotlib installations, my guess is that there is a 
bad afm font file somewhere on your system--in which case, it is not 
clear that upgrading to Lion would help.  There is another thread on the 
mailing list right now about a possibly similar problem. Fonts and Macs 
are outside my domain, but with that caveat, I suggest that instead of 
"upgrading" you try comparing the the collection of fonts on your work 
machine to that on your home machine.  Maybe something you installed on 
your home machine included a bad font file that mpl is finding.

Eric

>
> Thanks,
> Steve
>
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
>
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

All,

On my iMac at work running 10.6.8, I did a brew-based installation of Python 2.7.2. I used pip to install scipy, numpy and then matplotlib. The last didn't work right so I scoured the internets to find out what to do. The first solution I found suggested doing a git clone of the repository and running python setup.py build then python setup.py install. That worked just great.

At home, I tried the same thing on my MBP running 10.6.8. When I got to the compile matplotlib step, the fix from above didn't work. So I started trying other solutions I had found. Many of them "worked", however, when I went to run this simple script:

import matplotlib.pylab as plt
from scipy.stats import norm

I got this error:

Traceback (most recent call last):
  File "plot.py", line 1, in <module>
    import matplotlib.pylab as plt
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/pylab.py", line 221, in <module>
    from matplotlib import mpl  # pulls in most modules
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/mpl.py", line 2, in <module>
    from matplotlib import axis
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/axis.py", line 10, in <module>
    import matplotlib.font_manager as font_manager
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py", line 1323, in <module>
    _rebuild()
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py", line 1273, in _rebuild
    fontManager = FontManager()
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py", line 997, in __init__
    self.afmlist = createFontList(self.afmfiles, fontext='afm')
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py", line 565, in createFontList
    prop = afmFontProperty(fpath, font)
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/font_manager.py", line 501, in afmFontProperty
    weight = weight_as_number(font.get_weight().lower())
  File "/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/matplotlib-1.2.x-py2.7-macosx-10.4-x86_64.egg/matplotlib/afm.py", line 464, in get_weight
    return self._header['Weight']
KeyError: 'Weight'

Googling did not reveal a single occurrence of this error reported anywhere.

And so I would move on to the next instructions for compilation including the original make.osx instructions...and while the compilations succeeded, I still got the same error. Finally I decided to try the Enthought completely pre-compiled and packaged installation. Same problem.

I'm at a loss. I even completely erased my /usr/local/ directory so that everything would be consistently installed via Homebrew. But no matter what I do, I end up with the same problem.

I'm considering that something is wrong with my Snow Leopard installation and perhaps (reluctantly) upgrading to Lion, something I haven't really felt compelled to do. I'm hoping that there is a setting that I neglected.

Ideas? 


Thanks,
Steve

On Fri, 21 Oct 2011, Paul Ivanov wrote:

> Is there a particular reason you just upgraded to a version of matplotlib
> that is almost 2 years old now? Matplotlib 1.1.0 was released a few weeks
> ago,

Paul,

   Yes, the reason was 0.99.1.2 was on the SlackBuilds.org site, so I didn't
check to see if it was the current version.

> ... so it's strange that you did not upgrade to it, or at least to 1.0.1,
> which came out in January.

   I just did: 1.1.0 is now installed, but I still have the same problem
trying to run my model.

> I'm not certain that the issue you're running into has been fixed, but
> there have certainly been lots of changes. I also want to make sure that
> there isn't some stale pointer to an old version of matplotlib out there -
> so can you let us know what procedure you used to do the upgrade?

   I modified the matplotlib.SlackBuild script to remove the old patch and
the non-existant file names INTERACTIVE and KNOWN_BUGS. It built and
upgraded just fine.

   Ben's been helping by asking for information that might assist in
isolating the source of the problem. Since I am now using version 1.1.0 I'll
resend the error report.

   There are multiple lines reading:

Found an unknown keyword in AFM header (was Underline)

followed by the traceback:

Traceback (most recent call last):
   File "./eikos.py", line 6, in <module>
     from modelPage import modModel
   File "/home/rshepard/development/trunk/modelPage.py", line 9, in <module>
     from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as
FigureCanvas
   File
"/usr/lib/python2.6/site-packages/matplotlib/backends/backend_wxagg.py",
line 20, in <module>
     from matplotlib.figure import Figure
   File "/usr/lib/python2.6/site-packages/matplotlib/figure.py", line 18, in
<module>
     from axes import Axes, SubplotBase, subplot_class_factory
   File "/usr/lib/python2.6/site-packages/matplotlib/axes.py", line 14, in
<module>
     import matplotlib.axis as maxis
   File "/usr/lib/python2.6/site-packages/matplotlib/axis.py", line 10, in
<module>
     import matplotlib.font_manager as font_manager
   File "/usr/lib/python2.6/site-packages/matplotlib/font_manager.py", line
1323, in <module>
     _rebuild()
   File "/usr/lib/python2.6/site-packages/matplotlib/font_manager.py", line
1273, in _rebuild
     fontManager = FontManager()
   File "/usr/lib/python2.6/site-packages/matplotlib/font_manager.py", line
997, in __init__
     self.afmlist = createFontList(self.afmfiles, fontext='afm')
   File "/usr/lib/python2.6/site-packages/matplotlib/font_manager.py", line
559, in createFontList
     font = afm.AFM(fh)
   File "/usr/lib/python2.6/site-packages/matplotlib/afm.py", line 304, in
__init__
     parse_afm(fh)
   File "/usr/lib/python2.6/site-packages/matplotlib/afm.py", line 292, in
parse_afm
     dcmetrics_ascii, dcmetrics_name = _parse_char_metrics(fh)
   File "/usr/lib/python2.6/site-packages/matplotlib/afm.py", line 176, in
_parse_char_metrics
     name = vals[2].split()[1]
IndexError: list index out of range

   I will certainly add diagnostic code requested by you, Ben, and anyone
else and report the results when trying to run the model. I do need to fix
this and have no idea what's behind the problem.

Thanks,

Rich

I want to do some corrections and alterations to my last mail, because
it troubles me.

2011/10/21 Friedrich Romstedt <fri...@gm...>:
> I believe the one and only solution would, if thought thru completely,
> unveil that we need functional approach to get better results.  In
> matplotlib, each type of structure is an object of a class, which is
> not callable mostly, and this means, you have to formulate each
> alteration explicitly.  It's not easy in this frame of thinking to get
> the flexibility we in fact want - this might be the reason why mpl is
> so monolithic with all its different kind of Artist objects ... with
> the counterparts in the Renderer objects and so on.

I in fact think the "one and only" solution is a very dangerous deceit.

There might be some advantages of a functional approach, but there are
also severe drawbacks, for instance, that you get rubbish tracebacks
if something goes wrong.

This I just wanted to say to prevent piping errors.

Friedrich

FILENAME:
/usr/lib/python2.6/site-packages/matplotlib/mpl-data/fonts/afm/pagko8a.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/ISO8859-2/Type1/afm/gatsm___.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/atmfonts/swzlighi.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/vogueb.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/atmfonts/cottagen.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/centoldi.afm
FILENAME: /usr/share/fonts/culmus/NachlieliCLM-Light.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/amhersti.afm
FILENAME: /usr/share/fonts/local/n021004l.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/atmfonts/casprofn.afm
FILENAME: /usr/share/fonts/local/bchr.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/lithon.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/atmfonts/bangkokn.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/scottn.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/Type1/l047016t.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/Type1/n019003l.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/Type1/c059036l.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/atmfonts/cosmic2n.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/expon.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/culmus/AharoniCLM-Bold.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/Type1/n019064l.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/Type1/UTBI____.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/local/n019024l.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /usr/share/fonts/atmfonts/liquidn.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/culmus/NachlieliCLM-LightOblique.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)
FILENAME: /home/rshepard/.fonts/atmfonts/bravon.afm
Found an unknown keyword in AFM header (was Underline)
Found an unknown keyword in AFM header (was Underline)

On Mon, Oct 17, 2011 at 3:59 PM, Rich Shepard <rsh...@ap...> wrote:
> On Mon, 17 Oct 2011, Benjamin Root wrote:
>
>> I only need the last line printed by that print statement.  I want to see
>> how the parsing failed.
>
> Ben,
>
>   Here are the last 3:
>
> Line: C 125 ; WX 273 ; N braceright ; B 55 -68 244 707 ;
> Line: C 126 ; WX 586 ; N asciitilde ; B 39 219 531 408 ;
> Line: C 127 ; WX 262 ; N  ; B 64 506 246 730 ;
>
>   I see there's no character in the last line. Isn't that interesting!

What's weirder, is that 127 is a control character (Delete), and not
meant to be a printable character.

Maybe you already figured this out in following up with Ben, but if
not, can you 'print fh.name' before the while 1: in
_parse_char_metrics so we find out which .afm file is the culrpit

-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

On Friday, October 21, 2011, Benjamin Root <ben...@ou...> wrote:
>
>
> On Friday, October 21, 2011, Paul Ivanov <piv...@gm...> wrote:
>> Hi Rich,
>>
>> On Mon, Oct 17, 2011 at 10:57 AM, Rich Shepard <rsh...@ap...>
wrote:
>>>   After a long hiatus I'm again working on an application and just
upgraded
>>> matplotlib from 0.98.5.2 to 0.99.1.2.
>>
>> Is there a particular reason you just upgraded to a version of
>> matplotlib that is almost 2 years old now? Matplotlib 1.1.0 was
>> released a few weeks ago, so it's strange that you did not upgrade to
>> it, or at least to 1.0.1, which came out in January. I'm not certain
>> that the issue you're running into has been fixed, but there have
>> certainly been lots of changes. I also want to make sure that there
>> isn't some stale pointer to an old version of matplotlib out there -
>> so can you let us know what procedure you used to do the upgrade?
>>
>> best,
>
> Paul,
>
> Apparently, a bunch of the back-n-forth between myself and the OR went
off-list.  The problem is with the AFM font files packaged with mpl.  afm.py
is doing the correct thing by failing to parse an invalid line.  However, I
don't know much about AFM files and where they come from package-wise to
know where to file a bug report.
>
> Cheers,
> Ben Root

Oops, sorry, I meant to say AFM files *not* packaged with mpl.

Ben Root

On Friday, October 21, 2011, Paul Ivanov <piv...@gm...> wrote:
> Hi Rich,
>
> On Mon, Oct 17, 2011 at 10:57 AM, Rich Shepard <rsh...@ap...>
wrote:
>>   After a long hiatus I'm again working on an application and just
upgraded
>> matplotlib from 0.98.5.2 to 0.99.1.2.
>
> Is there a particular reason you just upgraded to a version of
> matplotlib that is almost 2 years old now? Matplotlib 1.1.0 was
> released a few weeks ago, so it's strange that you did not upgrade to
> it, or at least to 1.0.1, which came out in January. I'm not certain
> that the issue you're running into has been fixed, but there have
> certainly been lots of changes. I also want to make sure that there
> isn't some stale pointer to an old version of matplotlib out there -
> so can you let us know what procedure you used to do the upgrade?
>
> best,

Paul,

Apparently, a bunch of the back-n-forth between myself and the OR went
off-list.  The problem is with the AFM font files packaged with mpl.  afm.py
is doing the correct thing by failing to parse an invalid line.  However, I
don't know much about AFM files and where they come from package-wise to
know where to file a bug report.

Cheers,
Ben Root

Hi Rich,

On Mon, Oct 17, 2011 at 10:57 AM, Rich Shepard <rsh...@ap...> wrote:
>   After a long hiatus I'm again working on an application and just upgraded
> matplotlib from 0.98.5.2 to 0.99.1.2.

Is there a particular reason you just upgraded to a version of
matplotlib that is almost 2 years old now? Matplotlib 1.1.0 was
released a few weeks ago, so it's strange that you did not upgrade to
it, or at least to 1.0.1, which came out in January. I'm not certain
that the issue you're running into has been fixed, but there have
certainly been lots of changes. I also want to make sure that there
isn't some stale pointer to an old version of matplotlib out there -
so can you let us know what procedure you used to do the upgrade?

best,
-- 
Paul Ivanov
314 address only used for lists,  off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7