-
Notifications
You must be signed in to change notification settings - Fork 397
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.
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
Question: No module named 'aws_lambda_logging' #2
Comments
Hmmm odd. tests weren’t failing when I made that change - Here’s where the
issue might be
https://github.com/awslabs/aws-lambda-powertools/blob/develop/python/aws_lambda_powertools/logging/logger.py
We might need to do an explicit “import .aws_lambda_logging”, or PyPi
doesn’t have the latest.
I’ll looking into that as soon as I’m back from holidays (Jan 8th).
Thanks for reporting it
…On Wed, 11 Dec 2019 at 15:13, Wilson Wang ***@***.***> wrote:
Tried the logging code from README and got the error:
{ "errorMessage": "Unable to import module 'service': No module named
'aws_lambda_logging'", "errorType": "Runtime.ImportModuleError" }
The lambda runtime is Python 3.7.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<aws-powertools/powertools-lambda#2>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZPQBCHFQFZADEJQTHO2MLQYCHKBANCNFSM4JZKIYDA>
.
|
I just had the same issue on my side, with the following error message in my Lambda logs:
This was solved by explicitely adding |
I’ve just come back from holidays and will publish a fix by end of this
week.
No need to add that library in the requirements, it’s a bad relative import
in the logger.py
…On Wed, 8 Jan 2020 at 14:57, Nicolas Moutschen ***@***.***> wrote:
I just had the same issue on my side, with the following error message in
my Lambda logs:
[ERROR] Runtime.ImportModuleError: Unable to import module 'main': No module named 'aws_lambda_logging'
This was solved by explicitely adding aws-lambda-logging in my
requirements.txt.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<aws-powertools/powertools-lambda#2>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZPQBBLIIMBXGRGXC3O4ITQ4XST3ANCNFSM4JZKIYDA>
.
|
heitorlessa
added a commit
that referenced
this issue
Jan 9, 2020
Fix has been published -- 0.3.1 is now fully working. Thanks for reporting @opiuman ! |
heitorlessa
referenced
this issue
in heitorlessa/aws-lambda-powertools-python
Mar 1, 2021
heitorlessa
added a commit
that referenced
this issue
Mar 3, 2021
* feat: initial working skeleton Signed-off-by: heitorlessa <[email protected]> * feat: use global lazy import for intellisense * fix: default lazy provider * chore: trigger CI #1 * chore: trigger CI #2 * chore: uncaught linting * feat: add minimum generic interface for Tracing Provider and Segment * fix: type hints * refactor: use JSON Schema as dict to reduce I/O latency * docs: changelog * test: add perf tests for import * test: adjust perf bar to flaky/CI machines * fix(pytest): enforce coverage upon request only Signed-off-by: heitorlessa <[email protected]> * chore: address PR's review * chore: correctly redistribute apache 2.0 unmodified code * chore: test labeler * refactor: lazy load fastjsonschema to prevent unnecessary http.client sessions
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tried the logging code from README and got the error:
{ "errorMessage": "Unable to import module 'service': No module named 'aws_lambda_logging'", "errorType": "Runtime.ImportModuleError" }
The lambda runtime is Python 3.7.
The text was updated successfully, but these errors were encountered: