-
Notifications
You must be signed in to change notification settings - Fork 331
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
Python: Only pass metadata that we need #1600
Conversation
Rather than serializing the entire workerd config into a JSON string and then deserializing it at runtime this makes another readonly file system so we can copy only the data that Python wants to look at. This will copy all Data, Text, and Python files once at startup into the MetadataReader since I am not sure about the lifespan of the capnp config and it seems easier to understand if we make the module own its data.
"pyodide.c++", | ||
"pyodide/pyodide.c++", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These should be merged together, or the second one given a more descriptive name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll leave that to a followup. But it would also be good to merge pyodide.h
and pyodide/pyodide.h
Rather than serializing the entire workerd config into a JSON string and then deserializing it at runtime this makes another readonly file system so we can copy only the data that Python wants to look at. This will copy all Data, Text, and Python files once at startup into the MetadataReader since I am not sure about the lifespan of the capnp config and it seems easier to understand if we make the module own its data.