-
Notifications
You must be signed in to change notification settings - Fork 56
RIO.Process is running an "original" instead of a symbolic link #217
Copy link
Copy link
Closed
Description
I'm not fully sure what's happening here, the same codebase started behaving differently once I've reinstalled my Ubuntu from 18.04 to 20.04 but maybe that's unrelated.
I'm using RIO.Process to run my python subprocess. The python I'm trying to run is located in virtualenv:
$ ls -lah /home/kb/workspace/emotive_conjugations/venv/bin/python
lrwxrwxrwx 1 kb kb 16 Apr 25 23:23 /home/kb/workspace/emotive_conjugations/venv/bin/python -> /usr/bin/python3
Once I'm running that python, I get an error, because what it actually does is it ends up running /usr/bin/python3 instead, because it's calling the findExecutable to resolve the name internally:
λ RIO.Prelude.Simple.runSimpleApp (RIO.Process.findExecutable "/home/kb/workspace/emotive_conjugations/venv/bin/python")
Right "/usr/bin/python3.8"
So, my question is, who is wrong here and how should I call a virtualenv'ed python executable properly? Thanks!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels