#79 closed enhancement (invalid)
removing need to set PYTHONPATH in the shell
Reported by: | James C. McPherson | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 0.0.7.x |
Component: | client | Version: | |
Keywords: | Cc: |
Description (last modified by )
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.
Attachments (1)
Change History (7)
Changed 10 years ago by
Attachment: | pythonpath.diffs added |
---|
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Resolution: | → invalid |
Status: | new → closed |
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.
comment:3 Changed 10 years ago by
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.
comment:5 Changed 10 years ago by
Milestone: | current → 0.0.7.x |
---|
comment:6 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/79
ahem ... that should by "../lib/python2.6" rather than "../lib/python". Unless you create a symlink during the installation process.