[GRASS-dev] [GRASS GIS] #2008: grass.script's find_program() can't find modules

GRASS GIS trac at osgeo.org
Sat Jun 22 23:25:05 PDT 2013

#2008: grass.script's find_program() can't find modules
  Reporter:  hamish    |       Owner:  grass-dev@…              
      Type:  defect    |      Status:  reopened                 
  Priority:  critical  |   Milestone:  6.4.4                    
 Component:  Python    |     Version:  svn-releasebranch64      
Resolution:            |    Keywords:  find_program()           
  Platform:  All       |         Cpu:  x86-64                   

Comment(by glynn):

 Replying to [comment:30 hamish]:

 > No idea about the reasoning for special xdg-open tests. But not
 understanding is a reason to keep it there, not to delete it.

 I'd say the opposite. Otherwise, we will continually accumulate cruft
 which no-one understands.

 > > I don't think that find_program() is appropriate for GUI applications.
 > mmmph, it either works or it doesn't. The use case shouldn't matter.
 e.g. the r.in.wms wxPython wrapper in GRASS 6 needs the `xml2` program to
 be present, and needs to gracefully fail out with a suggestion to run the
 module from the command line if it isn't there.

 Just in case it wasn't clear, I mean that it's not appropriate for testing
 for the existence of GUI programs, not that it shouldn't be used from GUI

 A test requires a yes-or-no answer in a reasonable space of time.
 Attempting to test for a program which runs interactively either produces
 a quick "no" or it hangs indefinitely.

Ticket URL: <http://trac.osgeo.org/grass/ticket/2008#comment:33>
GRASS GIS <http://grass.osgeo.org>

More information about the grass-dev mailing list