AWS Lambda: Unable to import module 'package/file': No module named 'util'
I am struggling to get module importing to work in AWS lambda using Python 3.
My file structure looks like this:
package:
stage1.py
__init__.py
util:
helper1.py
__init__.py
helper1.py is a simple util class:
def foo():
print("yes")
Within stage1.py I have the following lines that cause Lambda to throw an error when it is starting:
from util.helper1 import foo
foo()
Unable to import module 'package/stage1': No module named 'util'
Both __init__.py files are empty.
Sadly, I see that this works if I invoke the script locally. Frustrating is an understatement!
python aws-lambda python-3.6
edited Nov 15 '18 at 1:30
martineau
66k989178
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
add a comment |
I am struggling to get module importing to work in AWS lambda using Python 3.
My file structure looks like this:
package:
stage1.py
__init__.py
util:
helper1.py
__init__.py
helper1.py is a simple util class:
def foo():
print("yes")
Within stage1.py I have the following lines that cause Lambda to throw an error when it is starting:
from util.helper1 import foo
foo()
Unable to import module 'package/stage1': No module named 'util'
Both __init__.py files are empty.
Sadly, I see that this works if I invoke the script locally. Frustrating is an understatement!
python aws-lambda python-3.6
edited Nov 15 '18 at 1:30
martineau
66k989178
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
stage1.pyis being called by a handler in AWS Lambda
– Chad Van De Hey
Nov 15 '18 at 1:41
Invoking scripts a within a package like it was a standalone often doesn't work. Relative imports for the billionth time might be helpful (it has a lot of information on how packages work).
– martineau
Nov 15 '18 at 3:05
As you mentioned the directory structure, I created the same on the Lambda and it is working file. Can you please update the question with the screenshot of the directory structure in lambda?
– Srce Cde
Nov 15 '18 at 14:19
add a comment |
I am struggling to get module importing to work in AWS lambda using Python 3.
My file structure looks like this:
package:
stage1.py
__init__.py
util:
helper1.py
__init__.py
helper1.py is a simple util class:
def foo():
print("yes")
Within stage1.py I have the following lines that cause Lambda to throw an error when it is starting:
from util.helper1 import foo
foo()
Unable to import module 'package/stage1': No module named 'util'
Both __init__.py files are empty.
Sadly, I see that this works if I invoke the script locally. Frustrating is an understatement!
python aws-lambda python-3.6
edited Nov 15 '18 at 1:30
martineau
66k989178
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
I am struggling to get module importing to work in AWS lambda using Python 3.
My file structure looks like this:
package:
stage1.py
__init__.py
util:
helper1.py
__init__.py
helper1.py is a simple util class:
def foo():
print("yes")
Within stage1.py I have the following lines that cause Lambda to throw an error when it is starting:
from util.helper1 import foo
foo()
Unable to import module 'package/stage1': No module named 'util'
Both __init__.py files are empty.
Sadly, I see that this works if I invoke the script locally. Frustrating is an understatement!
python aws-lambda python-3.6
python aws-lambda python-3.6
edited Nov 15 '18 at 1:30
martineau
66k989178
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
edited Nov 15 '18 at 1:30
martineau
66k989178
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
edited Nov 15 '18 at 1:30
martineau
66k989178
edited Nov 15 '18 at 1:30
martineau
66k989178
edited Nov 15 '18 at 1:30
martineau
66k989178
66k989178
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
asked Nov 15 '18 at 1:19
Chad Van De HeyChad Van De Hey
1,037716
1,037716
stage1.pyis being called by a handler in AWS Lambda
– Chad Van De Hey
Nov 15 '18 at 1:41
Invoking scripts a within a package like it was a standalone often doesn't work. Relative imports for the billionth time might be helpful (it has a lot of information on how packages work).
– martineau
Nov 15 '18 at 3:05
As you mentioned the directory structure, I created the same on the Lambda and it is working file. Can you please update the question with the screenshot of the directory structure in lambda?
– Srce Cde
Nov 15 '18 at 14:19
add a comment |
stage1.pyis being called by a handler in AWS Lambda
– Chad Van De Hey
Nov 15 '18 at 1:41
Invoking scripts a within a package like it was a standalone often doesn't work. Relative imports for the billionth time might be helpful (it has a lot of information on how packages work).
– martineau
Nov 15 '18 at 3:05
As you mentioned the directory structure, I created the same on the Lambda and it is working file. Can you please update the question with the screenshot of the directory structure in lambda?
– Srce Cde
Nov 15 '18 at 14:19
stage1.py is being called by a handler in AWS Lambda– Chad Van De Hey
Nov 15 '18 at 1:41
stage1.py is being called by a handler in AWS Lambda– Chad Van De Hey
Nov 15 '18 at 1:41
Invoking scripts a within a package like it was a standalone often doesn't work. Relative imports for the billionth time might be helpful (it has a lot of information on how packages work).
– martineau
Nov 15 '18 at 3:05
Invoking scripts a within a package like it was a standalone often doesn't work. Relative imports for the billionth time might be helpful (it has a lot of information on how packages work).
– martineau
Nov 15 '18 at 3:05
As you mentioned the directory structure, I created the same on the Lambda and it is working file. Can you please update the question with the screenshot of the directory structure in lambda?
– Srce Cde
Nov 15 '18 at 14:19
As you mentioned the directory structure, I created the same on the Lambda and it is working file. Can you please update the question with the screenshot of the directory structure in lambda?
– Srce Cde
Nov 15 '18 at 14:19
add a comment |
1 Answer
1
active
oldest
votes
Thanks to some of the links sent above and my own (and necessary) research into how imports are handled in python, I figured out the issue regarding unavailable modules.
How I debugged my app in Lambda:
I attached this line of code to the top of the file
print("Name is ({})".format(__name__))
This gave me an output that could help me understand an make an educated decision on how to import the files in the util module. I saw an output for the stage1.py file was packager/stage1. This made the import code modifications easy to make.
I changed the imports in the stage1.py file to (using absolute path imports -- pep recommendation):
from packager.util.helper1 import foo
For whatever subjective reason, this link helped me understand the process the most.
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311115%2faws-lambda-unable-to-import-module-package-file-no-module-named-util%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks to some of the links sent above and my own (and necessary) research into how imports are handled in python, I figured out the issue regarding unavailable modules.
How I debugged my app in Lambda:
I attached this line of code to the top of the file
print("Name is ({})".format(__name__))
This gave me an output that could help me understand an make an educated decision on how to import the files in the util module. I saw an output for the stage1.py file was packager/stage1. This made the import code modifications easy to make.
I changed the imports in the stage1.py file to (using absolute path imports -- pep recommendation):
from packager.util.helper1 import foo
For whatever subjective reason, this link helped me understand the process the most.
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
add a comment |
Thanks to some of the links sent above and my own (and necessary) research into how imports are handled in python, I figured out the issue regarding unavailable modules.
How I debugged my app in Lambda:
I attached this line of code to the top of the file
print("Name is ({})".format(__name__))
This gave me an output that could help me understand an make an educated decision on how to import the files in the util module. I saw an output for the stage1.py file was packager/stage1. This made the import code modifications easy to make.
I changed the imports in the stage1.py file to (using absolute path imports -- pep recommendation):
from packager.util.helper1 import foo
For whatever subjective reason, this link helped me understand the process the most.
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
add a comment |
Thanks to some of the links sent above and my own (and necessary) research into how imports are handled in python, I figured out the issue regarding unavailable modules.
How I debugged my app in Lambda:
I attached this line of code to the top of the file
print("Name is ({})".format(__name__))
This gave me an output that could help me understand an make an educated decision on how to import the files in the util module. I saw an output for the stage1.py file was packager/stage1. This made the import code modifications easy to make.
I changed the imports in the stage1.py file to (using absolute path imports -- pep recommendation):
from packager.util.helper1 import foo
For whatever subjective reason, this link helped me understand the process the most.
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
Thanks to some of the links sent above and my own (and necessary) research into how imports are handled in python, I figured out the issue regarding unavailable modules.
How I debugged my app in Lambda:
I attached this line of code to the top of the file
print("Name is ({})".format(__name__))
This gave me an output that could help me understand an make an educated decision on how to import the files in the util module. I saw an output for the stage1.py file was packager/stage1. This made the import code modifications easy to make.
I changed the imports in the stage1.py file to (using absolute path imports -- pep recommendation):
from packager.util.helper1 import foo
For whatever subjective reason, this link helped me understand the process the most.
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
answered Nov 15 '18 at 21:50
Chad Van De HeyChad Van De Hey
1,037716
1,037716
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311115%2faws-lambda-unable-to-import-module-package-file-no-module-named-util%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
stage1.pyis being called by a handler in AWS Lambda– Chad Van De Hey
Nov 15 '18 at 1:41
Invoking scripts a within a package like it was a standalone often doesn't work. Relative imports for the billionth time might be helpful (it has a lot of information on how packages work).
– martineau
Nov 15 '18 at 3:05
As you mentioned the directory structure, I created the same on the Lambda and it is working file. Can you please update the question with the screenshot of the directory structure in lambda?
– Srce Cde
Nov 15 '18 at 14:19