Closed jmogarrio closed 1 year ago
It's not clear that we'll actually want to do this (at least not in the naive way of reading directly from Drive in the code). Per Nicholas, it's a standard practice to record functionality in a Colab notebook but to spin up local Jupyter environments. At least part of the motivation for that approach is that hosted runtimes are necessary to use local modules. On the flip side, the drive
import from google.colab
is only available on hosted runtimes. If we want to read from Drive, we might need a different approach.
I suspect this is obsolete, or likely tracked under some line item in the new tracker.
There's a few blockers here: