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
I think I like the idea of explicitly representing the venv in the Component DAG. Where would it attach? The command? Or the root Component?
I guess the root Component would be the closest to the system we have now (and is convenient because the Component usually has the requirements.txt in its repo). The VirtualEnv spec would probably have a repo too, right?
Flags that can be passed when creating a virtualenv should be supported.
I ran into this when i started an EC2 instance running a recent Ubuntu and ran:
The VirtualEnv got created with Python 3.10.4 interpreter, which we don't support yet.
One solution would be to make VirtualEnv a PCS
Component
with attributes:The text was updated successfully, but these errors were encountered: