Anyone want to fix things in mpld3?

People are actually using mpld3. It would be great if there was more progress addressing the many issues that this use has uncovered. Interested?

Thanks for your interest in this project. I think that all of these points can be addressed, but it would be helpful to have a minimal example of python code that generates the issue in point (1) reliably. The github issue tracker has discussions related to points (3) and (4), and something that might be related to point (1). For point (2), it would be great to have a specific example in mind also, so that we can be sure any solution reduces file size substantially without compromising graphically accuracy.

1. https://github.com/jakevdp/mpld3/issues/226 https://github.com/jakevdp/mpld3/issues/250
2. Would be good to add an issue: https://github.com/jakevdp/mpld3/issues/new
3. https://github.com/jakevdp/mpld3/issues/247
4. https://github.com/jakevdp/mpld3/issues/198

As far as when all of these issues will be addressed, that is a pitfall of certain open-source projects that you might already be familiar with from your work with [related project]… I suspect that each fix will require a few hours of debugging at least, with (2) being easiest and (4) being hardest. I have a long list of issues to address, and although I’m happy to put these on it, I never seem to make progress on any of them.

Pull requests are certainly welcome, and if you or your collaborators wants to make these improvements, the mpld3 project will be happy to incorporate them into the codebase.

–Abie