Python conflict

Adam Dershowitz dersh at alum.mit.edu
Wed Dec 2 10:22:21 PST 2009



On Dec 2, 2009, at 10:08 AM, Ryan Schmidt wrote:

> 
> On Dec 2, 2009, at 12:03, Adam Dershowitz wrote:
> 
>> I am trying to use a binary package that also relies on python.  But it seems to expect the default apple python to be installed.  So, I have run:
>> sudo python_select  python26-apple
>> 
>> Yet when I run the binary, I see the following:
>> Python 2.5.4 found.
>> 
>> Or, if I run a different version of the binary, I see:
>> Python 2.6.4 found.
>> 
>> The apple version that is installed on my system (10.6.2) is 2.6.1 while macports has installed 2.5.4 and 2.6.4.  So, it seems that the application that I am running is finding the macports versions and not the apple version even though I have run python_select.
>> 
>> I have macports 1.8.1 and have done a recent sync.  The application that I am trying to run is GRASS and I have been using this set of binaries:
>> http://www.kyngchaos.com/software:grass
>> (although I also tried this one:  http://www.public.asu.edu/~cmbarton/files/grass_mac )
>> 
>> The problem comes up when I am trying to use their wxpython interface.  These two builds include wxpython and expect to use the system version of python, I was told.  But clearly something is funny if I run python_select for the apple version yet they are finding the macports python.
> 
> I wonder how it is finding python, or if there is a way to tell it which python to use.

I don't know how it is finding it.  But when GRASS starts, it opens a terminal and reports some things.  One thing is the Macports versions of python.  But then if I go into that same terminal and type python, I see the version that is selected with python_select.
It is also strange that one of the binaries is finding the 2.5 while the other is finding 2.6.  I have also been in touch with the guys who built these binaries, and they are being helpful to try to track it down.  But the initial response was that there is just a conflict between what their wxPython sees as the Python is it supposed to use and what your systems sees as the proper Python to use.

But it must be that python_select is missing some way to "hide" the other versions.  Because they are being found.

> 
> Alternately, have you tried installing the grass port?

I have not because it is somewhat old.  (6.3, while I am using 6.4).




More information about the macports-users mailing list