You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, currently we test with matplotlib 1.3, and I know of many such test failures with 1.4. mpld3 relies on the private matplotlib class hierarchy, which changed between versions 1.3 to 1.4 (and will likely change again with 1.5). This is not meant to be accessed outside the matplotlib package, so hacks like mpld3 will break between versions.
There doesn't seem to be motivation/time among mpld3 developers and users to track-down and fix all these issues, so for the time being I'd suggest down-grading to matplotlib 1.3. Another option is for you to join the team contribute fixes – let me know if you'd like to be involved. In any case, once MEP25 happens, we can do a re-write of the package to use this serialization interface and then (hopefully) mpld3 will not be so tied to particular matplotlib versions.
After applying #37, there is one more failure in the above test. It looks like the result is a little different:
There's some extra text, and one less vertex in the last path.
The text was updated successfully, but these errors were encountered: