wasm_backend vs. html5_canvas_backend

[kasajian]

Does anyone know what the difference between wasm_backend vs. html5_canvas_backend?

• The readme doesn't say
• Google doesn't say anything
• Nothing on stackoverflow.
• None of old issues explain it
• Looking at the source, there's not comments on html5_canvas_backend as to why it exists, and the documentation for wasm_backend sounds like it can apply to both.

I am using html5_canvas_backend with pyodide, which runs on web-assembly. So then what is wasm_backend? Isn't all of this wasm?

Yes, I would like answer to this question, but more than that, how is someone new to this project supposed to figure out what the readme means by these two bullets:

• for the wasm backend,
• for the interactive HTML5 backend;

I feel like there's some document or wiki missing. Or perhaps, there's an entirely different git repository somewhere that has all this information.

Any info at all how to navigate this space would be greatly appreciated.

[ryanking13]

You can check the following blog post and Gsoc project proposal.

• https://blog.pyodide.org/posts/canvas-renderer-matplotlib-in-pyodide/
• https://summerofcode.withgoogle.com/archive/2019/projects/4683094261497856

cc: @madhur-tandon

[hoodmane]

This package is unmaintained. We're waiting on someone to pick up the maintenance, then we can provide some help with whatever context we have. Which admittedly isn't much.