ZachHandleyOriginal post
Moderator
Hey,
So I see in the starter templates that I can use different Python versions or what not, but how do I actually specify this? I can’t find it anywhere in the docs, and when I tried to deploy a python-3.11 function it errored on me. Additionally, when changing that 3.11 back to 3.9, it errors on build for a reason I do not understand
Bash
Installing collected packages: pyxb, urllib3, lxml, idna, charset-normalizer, certifi, requests, authorizenet, appwrite Running setup.py install for pyxb: started Running setup.py install for pyxb: finished with status 'error' error: subprocess-exited-with-error × Running setup.py install for pyxb did not run successfully. │ exit code: -9 ╰─> [383 lines of output] Found bundle in /tmp/pip-install-ebcfy4wo/pyxb_9e14f3fb3495400ba3fc1cd6c4bdf977/pyxb/bundles/common bunch of shit in the middle copying build/lib/pyxb/utils/activestate.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/domutils.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/templates.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/unicode_data.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/saxdom.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/fac.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/six.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/saxutils.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/utils/utility.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/utils copying build/lib/pyxb/exceptions_.py -> /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/datatypes.py to datatypes.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/__init__.py to __init__.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/content.py to content.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/basis.py to basis.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/facets.py to facets.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/saxer.py to saxer.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/xml_.py to xml_.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/binding/generate.py to generate.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/__init__.py to __init__.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/bundles/common/__init__.py to __init__.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/bundles/common/raw/__init__.py to __init__.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/bundles/common/raw/xlink.py to xlink.cpython-39.pyc byte-compiling /usr/local/build/runtime-env/lib/python3.9/site-packages/pyxb/bundles/common/raw/xhtml1.py to xhtml1.cpython-39.pyc [end of output] note: This error originates from a subprocess, and is likely not a problem with pip.error: legacy-install-failure
× Encountered error while trying to install package.╰─> pyxbSo yeah any help would be appreciated
Summary
The user is experiencing an error while building a Python 3.9 function and trying to use different Python versions. The error seems to indicate a memory problem. The user also mentions that they are unable to see runtimes other than the default ones when using the CLI and asks how to enable them.
Solution: To enable runtimes other than the default ones, the user needs to use the UI instead of the CLI. Additionally, the error code -9 may indicate low memory. The user should check the logs for an explanation as to why the package couldn't be installed.