Allow more flexibility in executable path resolving

[Tilix4]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

As an admin, I'd like to be able to specify dynamic paths to find executables on users' machines. For examble, I'd like to be able to write something like ~/subpath/to/my/app or $HOME/subpath/to/my/app (this is unix system syntax, but env vars could be handy even for Windows systems).

How would you imagine the implementation of the feature?

Add this simple line to

ayon-core/client/ayon_core/lib/vendor_bin_utils.py

Line 70 in 7d06cc0

:

executable = os.path.expandvars(os.path.expanduser(executable))

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

[BigRoy]

Makes sense. For what it's worth, PRs are welcome.

[m-u-r-p-h-y]

It is already possible

[iLLiCiTiT]

It is possible to use environment variables, but it is not possible to use user's home directory (~/).

[alainxi]

In executable path, environment variables do not work if the env vars were declared in the "Variants" environment (which would be very useful, as it allows to have different env var depending on the DCC version : 4.0, 4.2, etc...)

Example :

[alainxi]

But the same env var declared in the "Variants" environment, is correctly expanded when it is used in the main Blender env var field (above/outside the Variants part).

So, this works all right :

[iLLiCiTiT]

In that case it is not issue for ayon-core but for ayon-applications addon.

[alainxi]

Thanks. I have declared an issue here :

ynput/ayon-applications#51

(I was slightly highjacking the original poster here, so it's better to have my own issue anyway)

[Tilix4]

It is possible to use environment variables, but it is not possible to use user's home directory (~/).

I'm glad the env var works, thanks @m-u-r-p-h-y. But this syntax {ENV_VAR} seems to be an AYON syntax, it is not standard $ENV_VAR. Allowing this syntax would be handy.