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

[GRASS GIS]

#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 hamish):

 Replying to [comment:29 wenzeslaus]:
 > Anyway, in r56880 I have deleted the test in g.manual since I
 > don't see any reason for it.

 In r56882 I have put it back. It is nice to have the clearer error message
 on Linux (where the error could come up a lot), and in cases where
 GRASS_HTML_BROWSER is either unset of malformed. It may need to be
 improved or fixed, but it should be there.

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


 Glynn:
 > 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.


 wenzeslaus:
 > Diverging from the original ticked topic, the
 `GRASS_HTML_BROWSER=firefox`
 > blocks the command line even after r56880 when no firefox session is
 running.

 there was another ticket for that (probably several over the years),
 closed as invalid AFAIU. To mitigate the problem I guess we could white-
 list some known GUI browser names and selectively background them?

 > However, this is expected and I think there is no way how to avoid
 > this when we want (probably because of cmd line web browsers) to
 > use `execlp`.

 exactly, mainly for links & lynx; although I suppose some rare but
 possible scripted html2txt/html2tex variants could exist.


 regards,
 Hamish

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