[MacPorts] #37558: GNU radio examples scripts fail with ImportError: No module named gnu radio

[MacPorts]

#37558: GNU radio examples scripts fail with ImportError: No module named gnu radio
---------------------------+-------------------------
  Reporter:  mikem43190@…  |      Owner:  michaelld@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.2
Resolution:                |   Keywords:
      Port:  GNUradio      |
---------------------------+-------------------------

Comment (by michaelld@…):

 First, a few comments, for beginners or experts using MacPorts and/or GNU
 Radio:

 * Once installed by MacPorts, all of GNU Radio should "just work" without
 further setting your shell environment variables.

 * In your shell environment, "PYTHONPATH" should point to the "pythonX.Y"
 directory, which is generally inside of "lib". So, for example, the first
 entry of "/opt/local/lib" should really be "/opt/local/lib/python2.7";
 ditto for the rest.

 * MacPorts' Python 2.7 already sets its internal PYTHONPATH to include
 "/opt/local/lib/python2.7" and
 "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7",
 so you don't need to include those in your shell environment's PYTHONPATH.
 And, really, you don't even need to set the PYTHONPATH at all if you're
 just using MacPorts' provided Python.  You need it only for non-MacPorts'
 provided installs.

 * I -highly- recommend against using DYLD_LIBRARY_PATH or any other DYLD_*
 shell environment variables except for testing purposes (e.g., "make test"
 in some projects, after building but before installing). If you set the
 DYLD_LIBRARY_PATH in your shell environment, you are likely to mess up
 program execution somewhere down the line and it's -really- hard to debug
 these sorts of issues.

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