Keys.EXECUTABLE

[wolski]

I am wondering how much sense does this Key make.

All of it's use I see is:
exe = app_info.get(Keys.EXECUTABLE, 'myrimatch')

or
exe = app_info.get(Keys.EXECUTABLE, 'comet')

both in the prepare_run method.

The key can't be used in a workflow ini file since it definitely needs to be different for various apps.

I would think it is better to replace it with an app specific key (i.e. COMET_EXECTUBLE, MYRIMATCH_EXECUTABLE).

[lcb]

What about Keys.PATH? There could be a folder with many executables in there? On the other hand then the user could just set the normal %PATH% variable (for windows and unix).
So what about COMET_EXECUTABLE etc? Default would be "comet" assuming that you have comet in your path, or you set the full path by hand.

On 18 Nov 2015, at 14:36, Witold Wolski notifications@github.com wrote:

I am wondering how much sense does this Key make.

All of it's use I see is:
exe = app_info.get(Keys.EXECUTABLE, 'myrimatch')

or
exe = app_info.get(Keys.EXECUTABLE, 'comet')

both in the prepare_run method.

The key can't be used in a workflow ini file since it definitely needs to be different for various apps.

I would think it is better to replace it with an app specific key (i.e. COMET_EXECTUBLE, MYRIMATCH_EXECUTABLE).

—
Reply to this email directly or view it on GitHub.