On 10/07/2014 05:13 PM, Eric Firing wrote:
> 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 u
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
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 issue
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 interac
