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
{{ message }}
This repository was archived by the owner on May 23, 2025. It is now read-only.
The pip command used in the first basic/Tutorial notebook is malformed. See image below.
I can submit a PR fixing this, however, I can take the opportunity to improve it a little.
Using --upgrade when installing multiple packages together can lead to long install times because of pip backtracking. I stopped it after ~30 minutes.
I would suggest talking out --upgrade and using version numbers instead. These are the latest version numbers, and I've tested them in my local environment and SageMaker Notebooks too.
Also, it's not advisable to use !pip install <package> in Jupyter notebooks as it might not install packages in the same execution environment used by the notebook. For example, I have to use pip3 instead for this to work.
The code snippet below is how you can work around the different execution environments (along with version numbers).
I've tested it on my local environment, I'll run it on a SageMaker Notebook too to verify the changes are good. If you're happy with the changes, I can submit a PR. 🙂
The pip command used in the first basic/Tutorial notebook is malformed. See image below.

I can submit a PR fixing this, however, I can take the opportunity to improve it a little.
--upgradewhen installing multiple packages together can lead to long install times because of pip backtracking. I stopped it after ~30 minutes.--upgradeand using version numbers instead. These are the latest version numbers, and I've tested them in my local environment and SageMaker Notebooks too.!pip install <package>in Jupyter notebooks as it might not install packages in the same execution environment used by the notebook. For example, I have to usepip3instead for this to work.I've tested it on my local environment, I'll run it on a SageMaker Notebook too to verify the changes are good. If you're happy with the changes, I can submit a PR. 🙂