Hi,
I’m curious if anyone knows of a way to set Python 3 without using the SHOTGUN_PYTHON_VERSION env var on the local machine for TK configs that are being stored in SG (distributed)? I don’t see anything about this in the docs.
Cheers,
Scott
Hi,
I’m curious if anyone knows of a way to set Python 3 without using the SHOTGUN_PYTHON_VERSION env var on the local machine for TK configs that are being stored in SG (distributed)? I don’t see anything about this in the docs.
Cheers,
Scott
Hi @scottballard, have you tried setting python path in the [config]/core/interpreter_[platform].cfg file(s)? That seemed to do the trick for me.
From what I can tell SHOTGUN_PYTHON_VERSION is only used at startup by SG Desktop. The moment a project pipeline config is loaded it appears the python pointed to by the interpreter_[platform].cfg takes over. Easiest way to confirm is by launching the SG Python console from within Desktop.
Thanks for the reply @nico.vandenbosch. It was always my understanding that the [config]/core/interpreter_[platform].cfg file(s) shouldn’t be stored in the config that is uploaded to SG.
However, I just gave your suggestion a try, added the files to the uploaded config and it seems to work!! Many thanks! Enjoy the weekend