-
Notifications
You must be signed in to change notification settings - Fork 109
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
Dependencies management #114
Comments
I played around with that and found it was simpler to just re-download everything rather than deal with the complexity of Jupyter kernels and venvs. The |
Why is this closed? |
Would you rather leave it open? |
Hmmm, ah sorry at the time of my last comment I somehow didnt see your response, my bad. And btw I'm a big fan of your work in general! Great stuff! Maybe just to bounce ideas around lets keep it open: please detail what you have tried so far and whether you think its work investigating further. I might give it a go because it would speed up my pipeline dramatically (this is the most time consuming step right now). |
Since libraries are installed in the persistent storage space, is there a way to not have to redownload every dependency on each VM creation because its by far the slowest step. Talking about the "Install requirements and download repositories" step here.
Maybe an additional new code step used for "rebooting a previous environment with the persisted libraries and spin up Gradio" in one cell would be useful?
The text was updated successfully, but these errors were encountered: