Xpra: Ticket #79: removing need to set PYTHONPATH in the shell

I've got xpra running on a development build of Solaris 11. Getting started took a while because I forgot to set PYTHONPATH before invoking the xpra script.

To remove the need for this, I added the following lines to it:

-import sys
+import sys, os
+sys.path.insert(0,
+    os.path.realpath(os.path.join(os.path.dirname(__file__), "../lib/python")))

Full patches for each invocation script are attached.

Sun, 12 Feb 2012 23:05:33 GMT - James C. McPherson: attachment set

attachment set to pythonpath.diffs

Sun, 12 Feb 2012 23:37:53 GMT - James C. McPherson:

ahem ... that should by "../lib/python2.6" rather than "../lib/python". Unless you create a symlink during the installation process.

Mon, 13 Feb 2012 06:33:57 GMT - Antoine Martin: status, description changed; resolution set

status changed from new to closed
resolution set to invalid
description modified (diff)

Sorry, but you should be installing Xpra system-wide, in which case it will be in your PYTHONPATH:

python make_constants_pxi.py wimpiggy/lowlevel/constants.txt wimpiggy/lowlevel/constants.pxi
CFLAGS=-O0 python setup.py install

If you chose not to do that, then obviously you will need to adjust PYTHONPATH to match your environment, changing the code is not an acceptable solution.

Mon, 13 Feb 2012 06:48:15 GMT - James C. McPherson:

I note that sometimes on multiuser machines where you do not have root access, you do need to make that change, or write a wrapper script which sets PYTHONPATH for you. *shrug* The patch was offered in the hope that it might help somebody who came across a similar issue.

Mon, 13 Feb 2012 06:54:08 GMT - Antoine Martin:

r495 adds an INSTALL file with (hopefully) clearer information.

Mon, 20 Feb 2012 19:16:56 GMT - Antoine Martin: milestone changed

milestone changed from current to 0.0.7.x

Sat, 23 Jan 2021 04:44:57 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/79