Scripts not working due to pyenv initialisation in .bashrc

[paulgould]

Quick question - I'm setting up a production environment and running into an issue when I try to run the update_fx_prices script.

Pyenv is recommended in installation.md for managing multiple python version and I agree it's great for that purpose. But if you follow the installation instructions for pyenv here: https://github.com/pyenv/pyenv#installation then you're going to add:
eval "$(pyenv init -)" to you .bashrc script.

Since the pysystemtrade scripts call .profile and this in turn calls .bashrc. Every time you try to run a script like:
. /home/you-home-dir/pysystemtrade/sysproduction/linux/scripts/update_fx_prices
your currently active venv environment will be reinitialised and thus you'll receive the error:
ModuleNotFoundError: No module named 'syscore'.

I'm wondering how best to resolve, as I'm a linux/python newbie; whilst I can easily fix this by removing:
. "$HOME/.bashrc" from .profile
I was hoping someone with a bit more knowledge might have a better suggestion. Thanks!

[bug-or-feature]

Hi @paulgould, sorry, I don't know how to solve your issue. But I can offer some observations:

In my experience, the production docs for this project should be viewed more as a set of guidelines, rather than a set of explicit instructions. Basically, do what is necessary to make it work for you. Figure out the gist of what is supposed to be happening, and make that happen for your OS/distro/environment etc. This is particularly true for the code in sysproduction/linux/scripts and sysproduction/linux/crontab, in my view. Don't be worried if your solution looks different to what is in the repo. I hope that helps

[paulgould]

Thanks for the advice @bug-or-feature, I'll take that approach then!

[j1404]

@paulgould How did you fix this?