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
Python workers: pgwasm working in local dev but failing in remote dev and deployment #1973
Labels
python
Issues/PRs relating to Python Workers
Comments
The error for remote dev looks like this:
But, as I said, it works fine for local dev. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been trying to connect a PG DB using pgwasm (which is based on pg8000 plus wasmsockets).
Since
requirements.txt
isn't supported yet, the necessary packages are bundled in a locallib
folder, and I made some very small patches to pgwasm here (I added ato_py()
call, and removed imports of some packages that aren't needed in my case).This is now running nicely in the local dev environment, but failing at deploy-time for non-local dev and deploy. Is this expected? Is there anything I can do to fix it?
Code is here: https://github.com/jawj/pypgworker
I can provide DB credentials privately if useful, or any Neon DB will do.
The text was updated successfully, but these errors were encountered: