-
-
Notifications
You must be signed in to change notification settings - Fork 787
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build orjson for pyodide #1282
Comments
The Rust-C interop story when compiling to webassembly isn't very good.
I've looked into this a few months ago and it go too far; iirc they use
a different C ABI.
|
What's the status with this one? Not sure if it was handled or not as I'm getting: @hoodmane, I see that you took care of the Rust part, does it mean that the orjson package is just missing or is it something else? Thanks |
It's probably straight forward. I'll look into it. What's the difference between orjson and ujson? As I understand they are both rust json libs? |
Yes, both orjson and ujson are Rust libraries for working with JSON data, but they have some differences in terms of their features, performance, and use cases. Features Performance Use cases Also see: |
Well it builds first try no problem. |
@hoodmane Does it mean that you should pack it and place under packages? |
Can you please share the current status of this one? Thanks! |
Well the status is that I think this is a straightforward task. I am currently distracted with other tasks, but if nobody else gets to it first I will get back to it at some point. |
@hoodmane, is it just adding a new package here with a corresponding If so, I can try and push such a PR. |
Yeah. You can use the Pyodide cli:
will generate the appropriate files. Then you need to add |
Closing as resolved via #4036 |
The project orjson offers significantly faster JSON encoding of objects than other Python packages (40x faster than the json package in many instances), with direct encoding of numpy arrays built in.
It would be nice if orjson could be built for pyodide. It is written in Rust, so that may be an issue.
The text was updated successfully, but these errors were encountered: