connect_subproc bug #13

Closed
tomerfiliba opened this Issue Mar 2, 2011 · 1 comment

Projects

None yet

1 participant

@tomerfiliba
Owner

Aviv Ben-Yosef Show activity 11/11/09
Hello,

I've been trying to use the rpyc.classic.connect_subproc function, and
found out that it passes Popen the string 'python' as the executable.
The problem is that on machines where 'python' is not the name of the
python executable, or isn't the executable that was used to execute
the code in the first place, it won't work.

This should be changed to sys.executable instead (I can send in the
patch if needed).

@tomerfiliba
Owner

fixes a28b882; closed by 7eb48a4; closed by 7eb48a4; closed by 7eb48a4; closed by 7eb48a4; closed by 7eb48a4; closed by 7eb48a4;

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment