Hi Joseph,

This seems to be a new behavior in matplotlib 2.2.0, which just came out officially this week.

I'm going to report it as a bug upstream to matplotlib but we will likely need to work around this on the yt side.

For now you can avoid this error by downgrading to matplotlib 2.1.2.

-Nathan

On Wed, Mar 7, 2018 at 8:48 PM, Joseph Smidt <josephsmidt@gmail.com> wrote:
I am using matplotlib 2.2.0.
_______________________________________________
yt-users mailing list -- yt-users@python.org
To unsubscribe send an email to yt-users-leave@python.org
_______________________________________________
yt-users mailing list -- yt-users@python.org
To unsubscribe send an email to yt-users-leave@python.org