Message380710
> For example, when I run the test exec on my macOS system, it is clear that the python3 being invoked is not the venv one but a different python3 altogether that shows up earlier on PATH.
In the test case I am interested in, PATH is not set to the venv at all. You're supposed to be able to run a script in a venv without activating. In my case, I am trying to write a wrapper script that behaves similarly to the symbolic link in test-venv/bin/python3 but that works if the path to the python3 interpreter changes in the future. (For example, one might install and then uninstall pyenv). |
|
Date |
User |
Action |
Args |
2020-11-10 20:21:28 | mppf | set | recipients:
+ mppf, ronaldoussoren, ned.deily |
2020-11-10 20:21:28 | mppf | set | messageid: <1605039688.09.0.751674424421.issue42312@roundup.psfhosted.org> |
2020-11-10 20:21:28 | mppf | link | issue42312 messages |
2020-11-10 20:21:28 | mppf | create | |
|