Python Dependency hell in windmill
Hello,
I have encountered an issue with the whole dependency setup in windmill.
I have a python script in windmil. I use phidata package. This package is accessed in python with 'from phi import ...'.
As you can see, the whole name phidata is not used but instead an alias 'phi'. Somehow this confuses windmill when it attempts to infer what package to identify.
I have attempted to fix this by following: https://www.windmill.dev/docs/advanced/dependencies_in_python
1) use CLI to add the workspace
2) wmill sync pull
3) add a requirements.txt and list all used packages (including phidata)
4) run wmill script generate-metadata
- I can see the lock file is being updated correctly
5) wmill sync push
6) all changes are correctly transfered to the windmill docker. However it does not register the changes being imposed on the lock file. It keeps the old dependencies (phi==0.6.7 this package is nonsense and does not exist) and not using the new (phidata==2.7.10)
Dependencies in Python | Windmill
In Windmill standard mode, dependencies in Python are handled directly within their scripts without the need to manage separate dependency files.
3 Replies
did you try that:
Dependencies in Python | Windmill
In Windmill standard mode, dependencies in Python are handled directly within their scripts without the need to manage separate dependency files.
Ah I had not seen that. Thanks sir! that did the trick. And a very smart method 👍