You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems it just needs to be added to /backend/parsers/windmill-parser-py-imports/src/lib.rs const STDIMPORTS, which seems to be a static list of imports.
For python3.10+, it would probably be better to populate this list dynamically. This method returns a list of standard lib module names - sys.stdlib_module_names. It might prevent future issues as new modules get added to the standard library. For instance "tomllib" was added in 3.11 and is also missing from the list.
To reproduce
Create a new script using Python
Import zlib
Attempt to save/publish
Expected behavior
It should correctly identify zlib as a standard lib, and not attempt to source from pip repo.
Screenshots
No response
Browser information
No response
Application version
CE v1.457.0-1-g8a446a658
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Python scripts that have:
import zlib
Error when deploying, as "uv" is trying to fetch it using pip. This is part of the python standard library, so this errors out.
https://docs.python.org/3/library/zlib.html
It seems it just needs to be added to /backend/parsers/windmill-parser-py-imports/src/lib.rs const STDIMPORTS, which seems to be a static list of imports.
For python3.10+, it would probably be better to populate this list dynamically. This method returns a list of standard lib module names - sys.stdlib_module_names. It might prevent future issues as new modules get added to the standard library. For instance "tomllib" was added in 3.11 and is also missing from the list.
To reproduce
Expected behavior
It should correctly identify zlib as a standard lib, and not attempt to source from pip repo.
Screenshots
No response
Browser information
No response
Application version
CE v1.457.0-1-g8a446a658
Additional Context
No response
The text was updated successfully, but these errors were encountered: