matplotlib-devel Mailing List for matplotlib

John,
As you may know, you're reverting the change Michael made sometime
ago. Michael said it is not a bug, but rather intended.
http://sourceforge.net/mailarchive/message.php?msg_id=6e8d907b0809031201p4bb0701eo23b3d294797a8766%40mail.gmail.com
So, I would appreciate if you reiterate this with Micheal before I
change back my scripts again.
Regards,
-JJ
On Thu, Sep 25, 2008 at 11:53 AM, John Hunter <jd...@gm...> wrote:
> On Thu, Sep 25, 2008 at 9:31 AM, Darren Dale <dsd...@gm...> wrote:
>> I noticed this morning that my Times and Palatino system fonts are not being
>> found anymore. I removed my fontManager.cache and ran my script with
>> verbose=debug, and it looks like creatFontDict found them, but then findfont
>> cant:
>
> I recently fixed another bug related to font finding when an explicit
> file name was passed -- I wonder if I broke a normal use case. It's a
> simple change shown in the diff below. Could you manually revert on
> your end and see if it makes a difference. If so, I'll have to find
> another solution to the problem I was fixing.
>
>
> johnh@flag:mpl> svn diff lib/matplotlib/font_manager.py -r6097:6098
> Index: lib/matplotlib/font_manager.py
> ===================================================================
> --- lib/matplotlib/font_manager.py (revision 6097)
> +++ lib/matplotlib/font_manager.py (revision 6098)
> @@ -955,7 +955,7 @@
> fname = prop.get_file()
> if fname is not None:
> verbose.report('findfont returning %s'%fname, 'debug')
> - return fname[0]
> + return fname
>
> if fontext == 'afm':
> fontdict = self.afmdict
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Tony S Yu wrote:
> Hi Eric,
> 
> Sorry for the late reply.
> 
> On Sep 27, 2008, at 8:56 PM, Eric Firing wrote:
> 
>> Actually, I think the most logical thing would be to let the default 
>> None give the old behavior, and require precision=0 to get the new 
>> behavior. What do you think? Is it OK if I make this change? It 
>> is more consistent with the old behavior.
> 
> I'm ambivalent about this change. On one hand, I think it makes a lot 
> more sense to have None give the old behavior and precision=0 to 
> ignore zero values in the sparse array (then precision would be 
> consistent for finite values and for zero).
> 
> On the other hand, I think ignoring zero values should be the default 
> behavior for sparse arrays (although, I definitely agree there should 
> be the option to plot all assigned values).
> 
> Would it be possible to make the change you suggest and also change 
> the default precision value to 0? (see diff below) This change would 
> also allow you to remove a lot of the special handling for 
> precision=None, since precision=0 gives the same result (I didn't go 
> this far in the diff below).
Good point. I made that change, but then made precision='present' be 
the value for sparse arrays to show all filled cells. precision=None is 
deprecated, but converted to 0.
Eric