Re: [matplotlib-devel] v1.4.1rc1 delayed :(

[Eric F. <ef...@ha...>]

I'm not sure what to do about 
https://github.com/matplotlib/matplotlib/issues/3621 either.  In 
general, I think it is best to have strings like this left in their 
native mode, not coerced to unicode, but that is contrary to the 
strategy decided upon when "from __future__ import unicode_literals" was 
adopted.

Mike, what do you think--are other projects going to run into this 
problem, triggered by a bug in LooseVersion?

Eric

On 2014/10/07, 11:03 AM, Michael Droettboom wrote:
> Thanks for working on all of these.  I just discovered another issue
> that really should be a blocker:
>
> https://github.com/matplotlib/matplotlib/issues/3622
>
> Mike
>
> On 10/01/2014 11:58 PM, Thomas Caswell wrote:
>> Hello all,
>>
>> We are going to miss the deadline on 1.4.1 as there is 2-3 blocker issues:
>>
>>     - #3470 / PR#3564  which started as issues with the macosx backend
>> and spiralled into discovering that we were only validating input to
>> rcparams about half of the time.
>>
>>    - #3505 The changes to disable interactive mode when not at a repl.
>> It turns out a lot of people use it and we should un-break them.
>>
>>    - #3517 which is related to non-ascii paths in font look up which
>> causes matplotlib to blow up on import.
>>
>> I am open to arguments that any of these should not be blockers.
>>
>> Tom
>>
>
>