-
Notifications
You must be signed in to change notification settings - Fork 118
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
Issues with Python 3.8 #22
Comments
Thanks for posting this, I did a lot of debugging and setting my runtime to 3.7 fixed. Any idea why it is breaking? |
I've been trying to solve this on #27 by directly using containers with no luck :( AWS Lambda does not provide a lot of information of the error so I don't know how to proceed, if you have any clue please share! :) |
I use serverless-chrome with Python 3.8 in AWS Lambda. In my case, I needed to install dependencies, and installing the latest official chrome solves the task. |
Using Python3.8, I get the following error:
Solution: Use Python 3.7 |
Hey, I was hoping to setup code profiling and more in depth monitoring of my lambda but that requires a python version >3.7., pychromeless is breaking over 3.7, Just adding this comment for visibility. |
Hi - if I setup pychromeless on a lambda instance with Python 3.6 or 3.7 runtimes it works fine. However, on 3.8 it errors out with a message saying that Chrome exited with status 127.
Do not need a fix for it but wanted to document this issue just in case other people have problems with it since for new Lambda machines the default is Python 3.8.
The text was updated successfully, but these errors were encountered: