up: Error with Python3 runtime
Prerequisites
- I am running the latest version. (
up upgrade) - I searched to see if the issue already exists.
- I inspected the verbose debug output with the
-v, --verboseflag. - Are you an Up Pro subscriber?
Description
Getting Unable to import module '_proxy': No module named '_proxy' in logs when deployed to staging/AWS.
Steps to Reproduce
Using Python3.6 runtime and proxy override of “python3 app.py”. Runs perfectly locally, but on deploy does not work and checking up logs gives Unable to import module '_proxy': No module named '_proxy'
Love Up?
Please consider signing up for Up Pro (https://up.docs.apex.sh/#guides.subscribing_to_up_pro) or donating via https://opencollective.com/apex-up/donate.
Slack
Join us on Slack https://chat.apex.sh/
About this issue
- Original URL
- State: open
- Created 6 years ago
- Reactions: 2
- Comments: 21 (9 by maintainers)
Yeah it’s a little confusing, I’ll try to get the python3.6 runtime working tomorrow
That would be awesome. Thanks!
On Thu, Jun 7, 2018 at 6:31 PM TJ Holowaychuk notifications@github.com wrote:
Currently it’s only possible to use the Node runtimes, just due to how an internal shim works, but I was planning on adding a Python one (issue #671).
It passes events to Up’s Go binary, basically just reading some JSON over stdio like https://github.com/apex/up/blob/master/internal/shim/index.js, but I haven’t tried writing one in Python yet