Skip to content
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.

Sign up for GitHub

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

imports #339

Closed
wants to merge 1 commit into from
Closed

imports #339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions advanced_functionality/kmeans_bring_your_own_model/kmeans_bring_your_own_model.ipynb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,6 @@
" \n",
"# Define IAM role\n",
"import boto3\n",
"import re\n",
" \n",
"from sagemaker import get_execution_role\n",
"\n",
Expand All @@ -77,9 +76,9 @@
"import urllib.request\n",
"import json\n",
"import mxnet as mx\n",
"import boto3\n",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any particular concern with importing boto3 twice? The advantage of having it in both cells is that if all your imports are in one cell, but you don't use the get_execution_role() function, you don't have to run it for future boto3 calls to work.

"import time\n",
"import io\n",
"import re\n",
"import os"
]
},
Expand Down