-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Enhancement ideas from JupyterLite #16
Comments
This is very much related to #7
So then the only thing that would work is
I guess these two could go together. Yes, indeed could be worth considering. So far the alternative is to use
Import time is after the package is installed, so I'm not sure this would be suitable for matplotlib which only cares about package installation. |
Thanks for carrying these over. To add more to an already heavy topic, we just landed wrapping As the goal is I was pleased to find that I think that these will give us a good way to document for content authors how to have a single
|
Yep. It's too bad it would be pretty hard to make this map to A related one: if this could be done in advance, and could have the importables data from |
Where "local" means, "the content owner shipped it", "not already "in This is not a security feature, as:
But rather, the use case is giving site owners a way to reduce the number of chances for un-reproducible behavior, and would be used in conjunction with a co-deployed pyodide and indexed wheels. Having it as an API would mean we could drop some patches. |
Yeah, yep, thanks for dbm = types.ModuleType("dbm") dbm.dumb = dbm.whichdb = None sys.modules["dbm"] = dbm # for ``jupyter_server`` anyio = types.ModuleType("anyio") sys.modules["anyio.to_thread"] = anyio.to_thread = types.ModuleType("to_thread") anyio.to_thread.run_sync = lambda: None sys.modules["anyio"] = anyio So yeah, anything that would make that a little easier 😍 |
Right, it's true. If there would be a place in pyodide itself to do this, that would be fine as well. But in general, "if a package gets installed, we want to do these things before/slightly after it imports" would be a lovely thing to be able to signal without forcing it to be installed to do so. |
This was implemented in #26 |
Welp, I've gone and started down the road of generating I haven't investigated the solution from #26, as handling mocks as actual wheels (e.g. 3.6kb of |
As summarized in pyodide/pyodide#3093 (comment) by @bollwyvl there are a number of features in piplite/JupyterLite built on top of micropip, some of which could make sense to move upstream, now that this package is standalone,
The text was updated successfully, but these errors were encountered: