xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #590


Ignore:
Timestamp:
06/07/14 13:38:34 (7 years ago)
Author:
Antoine Martin
Comment:

Does the Xpra shell script (found in Xpra.app/Contents/MacOS) continue to work if the exports are taken out? (looks like it should)

BTW, I fail to see what conda has to do with it. Where shall I be looking?

(alternatively, we could replace the PYTHONPATH modifications with more embedded python code that modifies sys.path instead)

Why things are done this way at present:

  • all the startup scripts we use were copied from the gtk-osx ones
  • Xpra must use its own copy of Python and the dozens of libraries it relies on, and the only way to do that on OSX is to bundle them, and then to use them we need to tell Python where to find them

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #590

    • Property Owner changed from Antoine Martin to Antoine Martin
    • Property Status changed from new to assigned
  • Ticket #590 – Description

    initial v1  
    22
    33I was testing Xpra in my Mac OS X  environment and was surprised to see this error:
    4 
     4{{{
    55    Traceback (most recent call last):
    66    File "/Users/krader/bin/ssh", line 10, in <module>
     
    99        import argparse
    1010    ImportError: No module named argparse
    11 
     11}}}
    1212The case is the Xpra shell script wrapper exports PYTHONHOME and a modified PYTHONPATH. I happen to have a python wrapper around the /usr/bin/ssh command in my PATH and it was broken by those environment vars. Those environment vars are not necessary and should not be set. See, for example, how Conda (http://conda.pydata.org) handles this.