Hello all. We have a Dagster setup that uses Poetry to manage the virtual environment. This is our `workspace.yaml`:

load_from:
  - python_package:
      package_name: pipeline
      executable_path: .venv/bin/python

Everything works great on Linux, but Windows uses a different path to the Python binary:

load_from:
  - python_package:
      package_name: pipeline
      executable_path: .venv/Scripts/python

Maybe this is more of a Poetry question..

Hi Archie, for now all I can recommend is that you use the same path on windows and unix or use different workspace.yaml files for the two platforms. A possible future solution we could implement is environment variable interpolation (so you could specify

executable_path

in an env var), but we don’t support that currently.

Using the same path doesn't seem to be an option, see this commit. It seems like our Windows devs will have to do a lol of git stash pop 🙂 We've managed to avoid any environment variables thus far. It would be nice if something like this worked (check each path sequentially):

load_from:
  - python_package:
      package_name: pipeline
      executable_path:
        - .venv/bin/python
        - .venv/Scripts/python

maybe you could use a symlink at a standard path? Still a pain but better than the alternatives

That's a good idea thanks! I'll look into this.