[MacPorts] #24451: Not able to 'import Scientific' after successfull macports installation of py26-scientific

MacPorts noreply at macports.org
Tue Apr 13 06:39:39 PDT 2010


#24451: Not able to 'import Scientific' after successfull macports installation of
py26-scientific
------------------------------+---------------------------------------------
  Reporter:  torgi@…          |       Owner:  adfernandes@…           
      Type:  defect           |      Status:  closed                  
  Priority:  Normal           |   Milestone:                          
 Component:  ports            |     Version:  1.8.2                   
Resolution:  worksforme       |    Keywords:                          
      Port:  py26-scientific  |  
------------------------------+---------------------------------------------
Changes (by adfernandes@…):

  * status:  reopened => closed
  * resolution:  => worksforme


Comment:

 I  can offer a couple of suggestions; if they don't work, then filing a
 possible bug with `python_select` is a good idea. I stopped using
 `python_select` and `gcc_select` a while a go because I would constantly
 discover applications ignoring paths, versions, etc. Now I just specify
 everything explicitly. That's just my casual opinion, by the way, and
 should '''not''' be taken as an implicit statement that `python_select` is
 buggy!

 For example, try running your scripts as `python2.6`. ''Usually'' that
 will run `/opt/local/bin/python2.6`, and you can check that with `which
 python2.6`. Depending on where `/opt/local/bin` is on your search path,
 `python` may be the system interpreter instead of the macports one,
 regardless of what `python_select` has done.

 So (1) try running python as `python2.6`. (2) Try `sudo python_select -d
 python26` and make sure it appears to have worked. (3) Try always invoking
 python as `/opt/local/bin/python2.6` and see if the import problem goes
 away. Also, if `python_select` succeeds, try running python as
 `/opt/local/bin/python` directly - explicit paths are your friends.

 I suspect, given your description of your problem, that somehow the system
 python is being run, somehow. The explicit path to macports will help
 diagnose where and why this is happening. Good luck!

-- 
Ticket URL: <http://trac.macports.org/ticket/24451#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list