Serverless Stack

(SOLVED)

hi everyone!

how can `sst start` use `python` from local `conda` environment? It keeps referring to global `/usr/local`  installation, which does not have custom packages

my guess is that `sst start` disregards my terminal environment and just uses an independent process that uses default values and therefore system python setup :thinking_face:

ok, solved myself after few trials and errors :slightly_smiling_face:

Short answer: `export PATH=/your/conda/env/python:$PATH`

`conda` by default amends PATH variable, but in my case `nvm` took precedence in the list, so system-wise python was found before the custom `PATH` was able to act

yet another export `PATH` helps to ensure that your `PATH` is always first, although can make duplications

As a side note, none of us have in-depth Python knowledge on the team. If you find anything weird with the python setup, feel free to bring it up.