Enforce system python in RPC calls#37
Conversation
As the RPC is executed with the user 'user', its PATH may point to a another python than /usr/bin/python3 with the right modules installed from the package manager. In this case the RPC fail with an import error. This commit enforce the use of the system python.
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026021104-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026020304-devel&flavor=update
Failed tests8 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/166096#dependencies 33 fixed
Unstable testsDetailsPerformance TestsPerformance degradation:12 performance degradations
Remaining performance tests:98 tests
|
marmarek
left a comment
There was a problem hiding this comment.
I think NixOS folks won't be happy about this change, but everywhere else it's correct thing to do
I have this issue that my user space may use another python than the system one,
leading to import errors.
It is not totally clear if I should bear the responsibility of the default
python used by my userspace or if the RPC call should always use the system
python anyway, as their dependencies are installed by the package manager.
I tend to think the second.