During the scipy 2024 tutorial, Codespaces was a bit finicky.
-
The current instructions to auto-launch jupyterlab, ctrl-click the URL was a bit cumbersome. it's necessary to copy and paste the token printed in the terminal. An easier approach seems to be launch the codespace, then add ?editor=jupyterafter the codespace has launched into the default vscode
-
If using jupyterlab the codespace seems to stop periodically, requiring a restart (~3 times in 4 hours) In other tutorials running via vscode this didn't seem to be happending. codespaces still list running jupyterlab as 'beta' so maybe this is an issue that will be worked out over time.
During the scipy 2024 tutorial, Codespaces was a bit finicky.
The current instructions to auto-launch jupyterlab, ctrl-click the URL was a bit cumbersome. it's necessary to copy and paste the token printed in the terminal. An easier approach seems to be launch the codespace, then add
?editor=jupyterafter the codespace has launched into the default vscodeIf using jupyterlab the codespace seems to stop periodically, requiring a restart (~3 times in 4 hours) In other tutorials running via vscode this didn't seem to be happending. codespaces still list running jupyterlab as 'beta' so maybe this is an issue that will be worked out over time.