You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the fallback runtime version temporarily allows access to the last version of the runtime before the upgrade described above, and is available until mid-March. Its purpose is to provide a temporary mechanism for users to more smoothly upgrade their notebooks to be compatible with Colab’s current runtime version. This is available from the Command Palette via the "Use fallback runtime version" command when connected to a runtime. Of note, this setting does not persist across sessions – the command will need to be invoked on each new session.
The text was updated successfully, but these errors were encountered:
Once the upgrade rolls out on Colab instances, can you reply to this issue saying that the upgrade is live, so that anyone who subscribed to the issue gets notified about that?
We can track the backend-info repository, but (as you note there) there typically is a delay of a few days between the commit there and the actual deployment on Colab instances.
Upgrade to Python 3.11
To provide additional features from Python 3.11 to our users, Colab will upgrade to Python 3.11 in early January. This upgrade provides benefits for the packages we pre-install in our runtime, and brings Colab into alignment with the cadence of final regular bug fix releases for Python versions.
Colab’s fallback runtime version
Using the fallback runtime version temporarily allows access to the last version of the runtime before the upgrade described above, and is available until mid-March. Its purpose is to provide a temporary mechanism for users to more smoothly upgrade their notebooks to be compatible with Colab’s current runtime version. This is available from the Command Palette via the "Use fallback runtime version" command when connected to a runtime. Of note, this setting does not persist across sessions – the command will need to be invoked on each new session.
The text was updated successfully, but these errors were encountered: