Our company uses 2 UniData accounts, one for production (/ud/PRODUCTION) and the other for testing new features (/ud/TEST). Is there a way to configure UniData's python implementation so that it gives preference to python packages based on what account a user is in? For example, I might have a production version of a python file (usefultool.py) with a callable function in it called 'dothistask'.
print('I did it')
return 'useful value'
and in a uniBasic program, I could access this function by running
VALUE = PyCallFunction('usefultool','dothistask')
This package is located in /ud/PRODUCTION/PP. But I want to add a feature or function to this package, but don't want to affect production implementation. So I add this python file to /ud/TEST/PP. Unfortunately, there doesn't seem to be a way to make each account prefer one directory over another when importing a function, so operations in the TEST account continue to favor the package version present in the production directory. My custom .pth file:
What's the best-practice way to keep these concerns separate? Separating our TEST account to its own VM/server, while probably most ideal, isn't an option.